On 6/6/06, Matthew Claridge <mclaridge@xxxxxxxxxxxxx> wrote:
on 06/06/2006 15:16 Joshua Slive said the following:
> On 6/6/06, Matthew Claridge <mclaridge@xxxxxxxxxxxxx> wrote:
>
>> Apache does send a Cache-control header of "max-age=0", which if I'm
>> right means it isn't updatiing the expiry time?
>
>
> It means the content is marked as expired. What mod_expires config
> are you using?
>
> Joshua.
<Location /images/>
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg A432000
ExpiresByType image/jpeg A432000
ExpiresByType image/gif A432000
ExpiresByType image/png A432000
ExpiresByType image/ico A432000
</IfModule>
</Location>
Seems like you have something else weird going on. The config used on
www.apache.org is
ExpiresActive On
ExpiresDefault A86400
And yet I get updated (non-zero) cache-control headers on 304 responses:
telnet www.apache.org 80
Trying 192.87.106.226... Connected to www.apache.org. Escape character is '^]'. GET / HTTP/1.1 Host: www.apache.org If-Modified-Since: Thu, 01 Jun 2006 14:07:19 GMT HTTP/1.1 304 Not Modified Date: Tue, 06 Jun 2006 14:31:19 GMT Server: Apache/2.2.0 (Unix) mod_ssl/2.2.0 OpenSSL/0.9.7g ETag: "20122-331e-4152a2fa513c0" Expires: Wed, 07 Jun 2006 14:31:19 GMT Cache-Control: max-age=86400 So it looks like you have something else in your config that is resetting your cache-control headers. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|