[ http://issues.apache.org/jira/brows...ON-142?page=all ]

Graham Dumpleton updated MODPYTHON-142:
---------------------------------------

Description:
If a handler sets req.no_cache to be true, then Apache will internally add a
ppropriate "Expires" header. Also the  req.no_cache attribute is consulted b
y mod_cache to know when not to cache. The alternative is that a handler mus
t 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 a
dditionally set if standards change in any way.

Not entirely sure if req.no_local_copy attribute is somehow related. It some
how affects whether 304 errors are returned in some cases. Certain modules s
uch as mod_include set this, so no reason that a mod_python handler wouldn't
 want to set it also.

was:
If a handler sets req.no_cache to be true, then Apache will internally add a
ppropriate "Expires" header. Also the  req.no_cache attribute is consulted b
y mod_cache to know when not to cache. The alternative is that a handler mus
t 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 a
dditionally set if standards change in any way.

Not entirely sure if req.no_local_copy attribute is somehow related. It some
how affects whether 302 errors are returned in some cases. Certain modules s
uch as mod_include set this, so no reason that a mod_python handler wouldn't
 want to set it also.


> Make req.no_cache and req.no_local_copy writable.
> -------------------------------------------------
>
>          Key: MODPYTHON-142
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-142
>      Project: mod_python
>         Type: Improvement
>   Components: core
>     Versions: 3.2.8
>     Reporter: Graham Dumpleton
>     Assignee: Graham Dumpleton
>      Fix For: 3.3
[vbcol=seagreen]
>
> 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 m
ust 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 th
em 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 af
fects whether 304 errors are returned in some cases. Certain modules such as mod_inc
lude set this, so no reason that a mod_python handler wouldn't want to set it also.[
/vbcol]

[ Post a follow-up to this message ]