Re: [squid-users] Not caching?

On Sunday 08 July 2001 08:43 am, Duncan wrote:
> Hi.
>
> Here is an example of what i get in my access.log, after going to
> http://www.yahoo.com (not the first time).
>
> 10.0.0.0 - - [08/Jul/2001:13:43:34 +0100] "GET
> http://us.a1.yimg.com/us.yimg.co\m/i/ww/m5v5.gif HTTP/1.0" 304 262
> TCP_IMS_HIT:NONE
> 10.0.0.0 - - [08/Jul/2001:13:43:35 +0100] "GET
> http://us.a1.yimg.com/us.yimg.co\m/a/co/compaq_comp_corp/powered_by_whit
>e_95x30.gif HTTP/1.0" 304 262 TCP_IMS_HI\T:NONE
> 10.0.0.0 - - [08/Jul/2001:13:43:36 +0100] "GET http://www.yahoo.com/
> HTTP/1.0" \200 18164 TCP_MISS:DIRECT
> 10.0.0.0 - - [08/Jul/2001:13:43:37 +0100] "GET
> http://us.a1.yimg.com/us.yimg.co\m/a/pr/promo/anchor/hp_careers5.gif
> HTTP/1.0" 200 3565 TCP_MISS:DIRECT
>
> I see TCP_IMS_HITs, but no TCP_HITs? I'm not sure what I'm doing wrong
> here. Should I enable reload_into_ims?

No. Not only is it already an IMS (thus ignore-reload is the next step),
but that only affects directives in the request so, unless you hit
'reload' in your browser, it's a squid or server issue.

What do you have for your refresh_pattern lines?

> The TCP_MISS:DIRECT suggests that squid went diretly to yahoo.com to get
> the site, and not the cache? .. Any sugestions on how to prevent this,

Since the response lacks an Expires or Last Modified header (or just about
any headers at all), that page is not cachable.

        -- Brian
Received on Sun Jul 08 2001 - 13:55:15 MDT