[squid-users] Squid HIER_NONE state in access logs

[Alex Rousskov]

On 3/20/19 3:46 PM, Dave Mulford wrote:

> I'm trying to determine what would cause Squid proxy to log a
> TCP_MISS/200 with a HIER_NONE state in its access logs.  A sample line
> looks like this (I've masked some of the values):

> 1549073041.578 8 1.2.3.4 TCP_MISS/200 123456 GET
> https://www.example.com:8443/mysite.js - HIER_NONE/-

> Looking in the forums I found an answer [1] that says this state can be
> logged if collapsed_forwarding or iCAP/eCAP are used.  I'm using neither.

> What other conditions could cause a TCP_MISS/200 with a HIER_NONE?

1. Unknown(?) Squid bugs that do not relay origin server details to
access.log.

2. Delay pools are enabled (at Squid build time) and the response has
not been fully received/stored by Squid when this client came for it.
This is essentially a bug that was deliberately introduced to quickly
fix another bug. For background, see:

* https://bugs.squid-cache.org/show_bug.cgi?id=2096
* https://bugs.squid-cache.org/show_bug.cgi?id=1001

A better fix for bug 1001 is wanted. I am not aware of anybody working
on or sponsoring it right now.


HTH,

Alex.