Re: [squid-users] rerequesting and recaching

On Friday 01 June 2001 03:09 am, you wrote:
> Maybe you have users pushing that reload button, forcing Squid to bypass
> the cache?
>
> If you enable log_mime_hdrs then the requests will be logged in detail,
> allowing you to look for "no-cache" requests.

An excellent idea, indeed. Thank you.

It turns out there were many "download managers" making numberous no-cache
and/or range requests in parallel. It couldn't use the cached items, so
the requests ripped right through the squid.

Another slightly related question:
A 302 w/o an Expires header is considered not cachable, but does it affect
cached versions of that URL? IOW, if my back-end apache is showing this:

[01/Jun/2001:08:20:31 -0400] "GET /zips/m37b15b.zip HTTP/1.0" 304
[01/Jun/2001:08:20:32 -0400] "GET /zips/m37b15b.zip HTTP/1.0" 304
[01/Jun/2001:08:20:33 -0400] "GET /zips/m37b15b.zip HTTP/1.0" 304
[01/Jun/2001:08:20:34 -0400] "GET /zips/m37b15b.zip HTTP/1.0" 302

Will the next request from squid be an IMS (returning 304) or a MISS
(returning 200)?

Thanks again
        -- Brian
Received on Fri Jun 01 2001 - 15:45:06 MDT