You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/01/15 20:59:18 UTC
DO NOT REPLY [Bug 14376] -
mod_proxy overwrites Date header
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=14376>.
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=14376
mod_proxy overwrites Date header
------- Additional Comments From coad@measurement-factory.com 2003-01-15 19:59 -------
Having both Cache-Control: no-cache and Expires is
perfectly valid/legal. "no-cache" does not mean "do not
cache/store"; it means "revalidate on every request". Expires
refers to content freshness which is often a separate issue.
Some applications may be able to predict expiration times and may still
want to see all [validation] requests. Some caches
(think CDNs like Akamai or bookmark revalidation services) may use the combination to optimize their [caching] decisions.
Cache-control overrides Expires:
The presence of an Expires header field with a date value of some
time in the future on a response that otherwise would by default be
non-cacheable indicates that the response is cacheable, unless
indicated otherwise by a Cache-Control header field (section 14.9).
Since this is not really realted to Date header changes, I will
probably submit a separate bug report.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org