On Thu, Nov 16, 2000 at 01:37:41AM -0500, Dan McCormick wrote:
>
> I came up with > some documentation below by sifting through the
> source code.
Excellent, thanks!
If a malformed Expires: prevents mod_proxy from caching a response (
> The response will then be
> cached UNLESS any of the following conditions are true
> (ap_proxy_cache_update):
[snip]
> - The response contains an Expires header that Apache can't parse
), why do they go to some lengths to make up for a malformed one (
> if the Expires time cannot be parsed and
> a Last Modified time exists from the previous step, then the Expires
> time is set to "now + min((date - lastmod) * factor, maxexpire)" (as
> noted in the source code comments)
)? I'm assuming that it can because that's a bit of extra logic that
wouldn't need to be there otherwise. Or maybe it's leftover code that
never fires.
I thought (not that I remember why) that it didn't need an Expires: header
and that it would make up a value of it's own based on the .conf settings.
- Barrie
