[squid-users] TCP_MISS/304 question

[Amos Jeffries]

On 14/10/2016 1:38 a.m., Yuri Voinov wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>  
> Hi gents.
> 
> I have very stupid question.
> 
> Look at this access.log entry:
> 
> 1476236018.506     85 192.168.100.103 TCP_MISS/304 354 GET
> https://www.gazeta.ru/nm2015/gzt/img/logo_footer.png -
> HIER_DIRECT/81.19.72.2 -
> 
> I'm see this:
> 
> http://wiki.squid-cache.org/SquidFaq/SquidLogs#HTTP_status_codes
> 
> Code 304 references to RFC 2616. Ok, opens it:
> 
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
> 

The reference is outdated. Current requirements are defined in
<https://tools.ietf.org/html/rfc7232#section-4.1>

...
> 
> According to RFC 2616, it comes from client's browser cache, make
> revalidation, discover content no changed and return 304 code.
> 
> So, it must means (exactly) CLIENT_HIT, right?
> 

No. Squid does not receive transactions that would match the meaning of
the tags CLIENT_HIT.


> My question is:
> 
> *Why Squid register this as TCP_MISS/304 in access.log, when logically
> expect TCP_CLIENT_HIT/304?*

This is a MISS on the Squid cache. A 304 from the server delivered to
the client.

It might be a CLIENT_IMS_UNMODIFIED or CLIENT_INM_UNMODIFIED if Squid
had codes for those cases.

Amos