Allen Pulsifer wrote:
I'm still wondering why mod_cache sets the expires header (or
some other
parameter, that causes the headers to be set).
Anything that goes in the cache has to have some expiration date--it can't
just live forever. The manual explains how its computed.
- And if the cach
> I'm still wondering why mod_cache sets the expires header (or
> some other
> parameter, that causes the headers to be set).
Anything that goes in the cache has to have some expiration date--it can't
just live forever. The manual explains how its computed.
> And why GET and HEAD requests get
Allen Pulsifer wrote:
I just tried "curl -I http://news.dds.dk/uploads/pics/broenonline.gif"; and
this is what I got:
Thank you for looking at the problem.
I even tried GET'ing the URL locally, so I couldn't figure out the
difference - until I did a HEAD request.
I get the "Expires" header
> I just tried "curl -I
> http://news.dds.dk/uploads/pics/broenonline.gif"; and this is
> what I got:
> ...
> Note, HTTP/1.1 request and no Expires header.
Since I didn't get the Expires header, is it possible that some other device
like a proxy is adding this header to your request?
Allen
--
> I have discovered, that an Apache 2.2.3 server sets an
> "Expires" header on our static content.
>
> I suppose Apache won't set the header in a "clean" install,
> but which other module could cause this header?
from modules\http\http_filters.c, line 1008:
/*
* Control cachability for
