On 28/08/2015 5:04 a.m., Jorgeley Junior wrote: > more logs: Aha! the first bit. What Squid sent to the server: > 2015/08/27 11:43:31.301 kid1| http.cc(2217) sendRequest: HTTP Server local= > 192.168.25.2:43127 remote=200.98.190.9:80 FD 66 flags=1 > 2015/08/27 11:43:31.301 kid1| http.cc(2218) sendRequest: HTTP Server > REQUEST: > --------- > GET / HTTP/1.1^M > Host: www.grupoatuall.com.br^M > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 > Firefox/40.0^M > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8^M > Accept-Language: pt-BR,pt;q=0.8,en-US;q=0.5,en;q=0.3^M > Accept-Encoding: gzip, deflate^M > Via: 1.1 firewall (squid)^M > X-Forwarded-For: 192.168.1.11^M > Cache-Control: max-age=259200^M > Now. Notice the FD number (66) on the line at the top there. And look for the very next set of headers with matching set of local=,remote=,FD values but titled "HTTP Server RESPONSE". That is apparently the reply that failed. * Compare the timestamps of the request/reply lines to see if it reminds you of any kind of timeout value you are aware of. Multiples of 30sec or 5min are common for timeout settings. * anything visibly wrong about the reply headers? Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
