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

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=21260

--- Comment #8 from Niklas Edmundsson <ni...@acc.umu.se> 2011-09-13 09:39:54 UTC ---
(In reply to comment #7)
> CacheMaxExpire as used in this patch seems to limit the max cache time to a
> default of 86400 seconds (1 day), which is broken - caches should definitely be
> allowed to cache for more than a day.

Both behaviors are probably wanted/needed by different users.

For us that have content that _might_ change we can live with a freshness-check
once a day in order to have the cache deliver stale content for a day maximum
(or whatever you set CacheMaxExpire to).

Others might want to have the current code behavior, I personally prefer the
documented one.

If I remember correctly passing the cache expire triggers a freshness check,
and if it's not-modified we're content with the cached body and write a new
header.
Doing this once a day by default is sane IMHO, no matter what Expires-header is
passed by the upper layer.

-- 
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