> The corresponding items in access.log are all TCP_MISS/200 (not 304). This
> occurs even after clearing the browser cache and restarting the browser and
> loading the site for the "first" time. I have checked site cacheability
> with a cacheability engine. I have changed refresh_pattern to give a
> positive minimum age to everything, and even added reload-into-ims.
Do you perhaps have a no_cache directive in your squid.conf blocking the content from being cached?
There are no no_cache directives in squid.conf.
Also verify the clock on your Squid server. If the clock is very much off then odd things will happen.
The clock is quite sane. The only (possibly) wierd thing is that I'm in the habit of having the hardware clock set in UTC rather than local time. Hopefully squid doesn't query the hardware clock...
Any more ideas?
TIA,
Tom
