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/02 05:43:49 UTC

DO NOT REPLY [Bug 21260] New: - CacheMaxExpire directive not enforced !

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

CacheMaxExpire directive not enforced !

           Summary: CacheMaxExpire directive not enforced !
           Product: Apache httpd-1.3
           Version: 1.3.27
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: jhroyer@joher.com


Hi,

The CacheMaxExpire directive is not enforced as stated in the documentation 
(quote: "This restriction is enforced even if an expiry date was supplied with 
the document").

After looking at the source of mod_cache.c you can see that the maxexpire value 
is only used IF the expiration date provided is bad AND the last modified date 
provided is good.

Basically if an expiration date is provided in the document fetched, the 
CacheMaxExpire value is ignored.

I assume it is a bug in the source rather than a bug in the documentation since 
I think that CacheMaxExpire directive must really be enforced...

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