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/07/08 07:15:16 UTC

DO NOT REPLY [Bug 21392] New: - Protocol Violation: Expires should be overridden by Max-age directive

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=21392>.
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=21392

Protocol Violation: Expires should be overridden by Max-age directive

           Summary: Protocol Violation: Expires should be overridden by Max-
                    age directive
           Product: Apache httpd-2.0
           Version: 2.0.46
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_cache
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: sragavan@novell.com
                CC: sragavan@novell.com


When the proxy server sends max-age and Expires for a response like

     Cache-Control: max-age=10
     Expires: <some future date>

After 10 seconds this response should be stale in the proxy cache. But
The server still responds from the cache because of Expires header. It is not 
overridded as per the RFC.

"If a response includes both an Expires header and a max-age
directive, the max-age directive overrides the Expires header, even
if the Expires header is more restrictive. This rule allows an origin
server to provide, for a given response, a longer expiration time to
an HTTP/1.1 (or later) cache than to an HTTP/1.0 cache."

When max-age is specified, the expiration comparison should not include EXPIRES 
header.

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