Hi Amos thanks for the reply . actually the sample i put is seems incorrect im supposed to push the request as below : 25/Jun/2018:12:22:16 +0100 4057 32.175.99.98 16993 188.157.235.133 2000 TCP_TUNNEL/200 224466 CONNECT www.google.com:443 dfrrew HIER_DIRECT/ www.google.com 2a00:1450:4009:815::2004 2406:a901:416f:bdd9:392:4b51:d110:c6b9 25/Jun/2018:12:22:17 +0100 3456 32.175.99.98 17317 188.157.235.133 2000 TCP_TUNNEL/200 211560 CONNECT www.google.com:443 dfrrew HIER_DIRECT/ www.google.com 2a00:1450:4009:815::2004 2406:a901:6963:b915:91dd:ac97:af6b:843e 25/Jun/2018:12:22:17 +0100 2351 32.175.99.98 17607 188.157.235.133 2000 TCP_TUNNEL/200 220144 CONNECT www.google.com:443 dfrrew HIER_DIRECT/ www.google.com 2a00:1450:4009:815::2004 2406:a901:d64b:2c12:29a0:3422:f505:a689 25/Jun/2018:12:22:17 +0100 2299 32.175.99.98 17491 188.157.235.133 2000 TCP_TUNNEL/200 174475 CONNECT www.google.com:443 dfrrew HIER_DIRECT/ www.google.com 2a00:1450:4009:815::2004 2406:a901:52f5:b367:b482:40da:36f7:7bf6 so above is what is what logs i say about . all what i need is to know if the request gone correctly or there was a captcha page is there any footprints can i look for to know ? like message reply size or so as connection encrypted many thanks > On 20 Jun 2018, at 8:02, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > > 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 > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
