Re: [squid-users] Reverse proxy woes

tor 2008-02-21 klockan 18:45 -0500 skrev Anthony Tonns:
> < HTTP/1.0 200 OK
> < Date: Thu, 21 Feb 2008 23:31:55 GMT
> < Server: Resin/3.1.3
> < Cache-Control: max-age=60, must-revalidate, proxy-revalidate
> < Expires: Thu, 21 Feb 2008 23:32:54 GMT
> < Content-Type: text/html; charset=iso-8859-1
> < X-Cache: MISS from devserver01.example.com
> < X-Cache-Lookup: MISS from devserver01.example.com:80
> < Via: 1.0 devserver01.example.com:80 (squid)
> < Connection: close
> Closing connection #0

1 minute expiry time and no cache validator.

Squid has a filter that by default requires objects to be fresh for 1
minute if there is no cache validator. This to avoid caching objects
which quite likely won't be reused.

In accelerator setups you probably want to make this a much shorter
limit. See minimum_expiry_time in squid.conf.

> But then all of a sudden I'll get this for a minute as the Age counter
> increments up to max-age, 60:

Since the response is just on the limit between what is allowed to get
cached or not I can imagine that minimal timing differences can make a
difference here.

Regards
Henrik