Re: [squid-users] Understanding the use of must-revalidate/proxy-revalidate

On Tue, 21 Sep 2010 10:53:37 +0800, Sean SPALDING <s.spalding_at_ecu.edu.au>
wrote:
> Hi all,
>
> I'm struggling with the configuration of a PHP based content management
> system served from Apache behind a squid 2.6 reverse proxy.
Specifically,
> it's serving out stale content, ie. responses that are past their
"Expires"
> time.
>
> I've added "must-revalidate" to the "Cache-Control" header but squid is
> still caching the (old) response. I thought it would re-cache the URL
after
> the "Expires" time. Is that not the case?
>
> Also note, the application is configured to send a "304 Not Modified"
> Status-Code where appropriate.
>
> This request was made at Mon, 20 Sep 2010 05:05:45 GMT but is still
being
> severed by squid hours after becoming "stale".

Looks like bug #7 biting. You will need to upgrade to the latest Squid 2.7
or 3.1 which fix this in various ways.

Amos
Received on Tue Sep 21 2010 - 03:19:27 MDT