[squid-users] Another squid log question (still from 2.6.STABLE18): TCP_HIT + DIRECT

[Amos Jeffries]

On 13/08/2016 3:30 a.m., Henry S. Thompson wrote:
> In e.g. yesterday's log file, for 950K valid http requests, I find about
> with 822K peer status DIRECT/...
> Of these, those with squid status some variant of _HIT break down as
> follows:
> 
>     115 TCP_HIT/200
>      49 TCP_IMS_HIT/304
>       8 TCP_MEM_HIT/200
>   12880 TCP_REFRESH_HIT/200
>      15 TCP_REFRESH_HIT/206
>   14566 TCP_REFRESH_HIT/304
> 
> I understand the REFRESH cases, but what about the first three?  Under
> what circumstances does a (non-REFRESH) cache hit none-the-less cause a
> fetch to an origin server?
> 

IIRC Squid-2 used DIRECT as a catch-all value when it didn't have a
better one to use.

My old memories could be wrong though. You will likely have to check the
code or an ALL,9 cache.log to find out why. None of the dev guys who
worked on Squid-2 hang out here anymore. It has been 8 years since that
version was deprecated.


PS. If this version is being forced on you by any particular vendors
product I suggest you send queries their way. Squid versions are
officially supported here for only a few years (1-3) with a bit of
'wiggle room' for things that haven't changed in the supported releases,
then any vendors who want to provide LTE releases of old Squid take up
the support burden for their particular release.

Amos