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

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.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://issues.apache.org/bugzilla/show_bug.cgi?id=21260





------- Additional Comments From Dick.Snippe@tech.omroep.nl  2006-04-26 14:07 -------
(In reply to comment #3)
> Has this bug been fixed in 2.0.x?   
>  
> Thanks. 

I'm using 2.2.0 and it appears that the bug hasn't been fixed.
Currently I have a setup with CacheMaxExpire 600, but I get answers from my
cache with "Age: 2294", so that can't be right.

It would appear that cache_util doesn't honour CacheMaxExpire at all. When
looking at modules/cache/cache_util.c, around line 298, I see:
    /* handle expiration */
    if (((smaxage != -1) && (age < (smaxage - minfresh))) ||
        ((maxage != -1) && (age < (maxage + maxstale - minfresh))) ||
        ((smaxage == -1) && (maxage == -1) &&
         (info->expire != APR_DATE_BAD) &&
         (age < (apr_time_sec(info->expire - info->date) + maxstale - minfresh)))) {
        const char *warn_head;

        warn_head = apr_table_get(h->resp_hdrs, "Warning");

        /* it's fresh darlings... */

i.e. nothing relating to CacheMaxExpire

The only references to CacheMaxExpire are in mod_cache.c, line 692 where Expires
headers are created based on last modified headers.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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