Summary: | 304 - Not Modified does not return Expires/Cache-Control headers | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Marc Jauvin <marc> |
Component: | mod_expires | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | CLOSED DUPLICATE | ||
Severity: | major | ||
Priority: | P3 | ||
Version: | 2.0.48 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Marc Jauvin
2003-12-01 20:42:44 UTC
Both responses look correct to me. From RFC 2616: 10.3.5 304 Not Modified [...] The response MUST include the following header fields: [...] - Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant So if the fields don't differ, they may or may not be sent, right? I guess it depends on what "previous response for the same variant" means... but why is Apache 1.3.X returning those headers? *** This bug has been marked as a duplicate of 24884 *** This is a valid bug. Try setting the ExpiresByType to "access plus 5 minutes". Every acccess should get a new Expires header but doesn't. Please see http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=106947094322141&w=2 for a summary of the problem. I'm still looking for the solution. This PR has been fixed in the 2.1-dev branch and has been suggested for backporting to the 2.0 stable branch. Thank you for using Apache and for submitting this report. |