https://issues.apache.org/bugzilla/show_bug.cgi?id=52120
Bug #: 52120
Summary: mod_cache edge case: uncacheable 304 sends cached
body, but not cached headers
Product: Apache httpd-2
Version: 2.3.14-beta
Platform: PC
OS/Version: Mac OS X 10.5
Status: NEW
Severity: normal
Priority: P2
Component: mod_cache
AssignedTo: bugs@httpd.apache.org
ReportedBy: minfrin@sharp.fm
Classification: Unclassified
When an attempt is made to freshen a stale entry in the cache, and the 304 Not
Modified response from the backend contains no ETag, no Last-Modified, and no
Cache-Control header, the following code path is followed:
X-Cache-Detail: "conditional cache hit: 304 was uncacheable though (s-maxage or
max-age zero and no Last-Modified or Etag; not cacheable); entity removed" from
...
In this case, because the 304 is technically uncacheable, we send the cached
copy once and invalidate the entry. What we don't do however is send the
original cached headers, just the headers from the 304, and in the process we
see headers like Content-Type being lost or replaced.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
|