httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24884] - When the response is 304 Apache doesn't include cache headers
Date Tue, 25 Nov 2003 09:27:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24884>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24884

When the response is 304 Apache doesn't include cache headers





------- Additional Comments From qnxuserit@yahoo.it  2003-11-25 09:27 -------
I found an old issue (http://www.apacheweek.com/issues/96-08-30)... seems to be 
an old problem:

<cut....>

Responses can also contain a definite time when the document will expire, in 
the Expires HTTP header. There are some cases where the expiry time of a 
document might change, even if the document itself has not changed. So a 304 
status message can include an updated expires time, which the browser should 
use to replace the expires time in it's cached copy of the file. Currently 
Apache does not send out the expires header on 304 status, which is required by 
HTTP/1.1. The problem with not sending out the expires header is that the 
browser still keeps the old expiry time, so it thinks the document has expired 
straight away. This will be fixed in the next release. 

<cut....>

Is there a work-around?

Thanks,
Fabio

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message