[ https://issues.apache.org/jira/browse/MODPYTHON-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Graham Dumpleton closed MODPYTHON-142. -------------------------------------- > Make req.no_cache and req.no_local_copy writable. > ------------------------------------------------- > > Key: MODPYTHON-142 > URL: https://issues.apache.org/jira/browse/MODPYTHON-142 > Project: mod_python > Issue Type: Improvement > Components: core > Affects Versions: 3.2.8 > Reporter: Graham Dumpleton > Assigned To: Graham Dumpleton > Fix For: 3.3 > > Attachments: MP142_20060305_grahamd_1.diff > > > If a handler sets req.no_cache to be true, then Apache will internally add > appropriate "Expires" header. Also the req.no_cache attribute is consulted > by mod_cache to know when not to cache. The alternative is that a handler > must know to set both: > req.headers_out['Cache-Control'] = 'no-cache' > req.headers_out['Expires'] = '-1' > It would be better to allow handlers to set req.no_cache as it isolates them > from any future changes in respect of special headers that may need to be > additionally set if standards change in any way. > Not entirely sure if req.no_local_copy attribute is somehow related. It > somehow affects whether 304 errors are returned in some cases. Certain > modules such as mod_include set this, so no reason that a mod_python handler > wouldn't want to set it also. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.