Re: pages not cached that should be

Paonia Ezrine wrote:

> 956242954.555 SWAPOUT 00000204 200 956242954 954530323 956329354 audio/x-wav 15338/15338 GET http://www.esportsplus.com/data/baseball/pcm/playball.wav
> 956243222.123 SWAPOUT 00000243 200 956243222 954530323 956329622 audio/x-wav 15338/15338 GET http://www.esportsplus.com/data/baseball/pcm/playball.wav
> 956243707.903 SWAPOUT 000002CC 200 956243708 954530323 956330107 audio/x-wav 15338/15338 GET http://www.esportsplus.com/data/baseball/pcm/playball.wav

Hmm.. this looks odd.. lots of SWAPOUT's, but no releases. However, I
have a vague memory of some bug forgetting to log RELEASE under certain
quite common conditions so maybe not..

Anyway, lets see what the first line above says:

Proxy Time: Thu Apr 20 15:02:34 2000 GMT
Request: GET http://www.esportsplus.com/data/baseball/pcm/playball.wav
Date: Thu Apr 20 15:02:34 2000 GMT
Last-modified: Fri Mar 31 19:18:43 2000 GMT
Expires: Fri Apr 21 15:02:34 2000 GMT

Looks good. The object should have been cached even without the explicit
expiry time (default pattern says 20% of modification age, which is ~4
days in this case)

Maybe there are clients preventing the caching? Try enabling
log_mime_hdrs to get the full request info in access.log.

--
Henrik Nordstrom
Squid hacker