Re: Transparent cache behaviour and complaining webdesigners

Hroi Sigurdsson wrote:
>
> I've set up a transparent squid cache which seems to be working fine
> most of the time. Though today several users complained about not being
> able to see the changes they made to their websites.
> They use IE for the most part and the all the sites in question are on
> Apache servers.

IE does not work well together with TCP hijacking caches. When it is not
configured to use a proxy it (correcly) assumes there is no cache in
between itself and the origin server, and hence does not indicate that
caches should be ignored when the user pushes reload.

> I thought squid always checked the Last-modified header on the remote
> end before sending the cached content?

Only if ypu configure it to.

The default configuration considers an object fresh for 20% of it's
modification age.

> How can i work around this without setting up cache deny acls for the
> poor webdesigners?

See refresh_pattern in squid.conf.

--
Henrik Nordstrom
Squid hacker