[squid-users] how debug google status codes in log file
Amos Jeffries
squid3 at treenet.co.nz
Wed Jun 20 05:02:00 UTC 2018
On 19/06/18 17:12, --Ahmad-- wrote:
> hello folks
> how debug google status codes in log file ?
>
see the FAQ
<https://wiki.squid-cache.org/SquidFaq/SquidLogs#access.log>
> in wiki i see we have :
>
> 1529368601.307 60038 184.154.133.146 TAG_NONE/503 0 CONNECT www.google.com.et:443 fifoxy HIER_NONE/- -
>
> the question is how can i see the http status code of connection in proxy ?
Which "the" ? there are possibly many connections used for each
transaction (aka access.log line).
The above log line says Squid spent 60sec on this transaction, no
servers were able to be connected to in that time.
Squid also *tried* to deliver a 503 HTTP status message to the client,
but 0 bytes got written. Probably a TCP RST got sent to the client
instead (eg. SSL-Bump "terminate" action).
The *debugging* to happen is nothing to do with status codes. It is
actions you need to perform to figure out why no server contact
happened, and/or why Squid thought it had to send an error.
That assumes that you do not already know what happened, and that it is
not something you wanted to configure (eg SSL-Bump terminate certain TLS
handshakes).
Amos
More information about the squid-users
mailing list