On 11/03/21 11:33 pm, Arjun K wrote:
Hi Alex/Team
The end user are receiving an error in the browser stating : "The site
can't be reached"and " <URL> took long time to respond ".
So can you assist me to include the custom log format which will provide
further details.
[Thu Mar 11 11:02:15 2021].001 119629 10.197.10.140 TAG_NONE/503 0
CONNECT <URL>.amazoncognito.com:443 - HIER_NONE/- -
First issue, "why does the error page get produced?"
1) that log entry says that Squid waited 119.6 seconds for the server
TCP connection to be setup. Before giving up and sending the client a
503 message.
Second issue, "why is the server connection so slow?"
A) There should not be a *URL* in the *domain name* part of CONNECT
requests. If that really is a URL instead of a hostname, that is very
likely your problem.
B) what happens in the network outside of Squid can have many different
effects on speed of TCP connection setup. Or packet loss can prevent
connections being setup at all.
C) problems with DNS server(s) can add to the delays during server
connection opening. That ranges from problems connecting to the DNS
server(s), outdated records being returned by them, and again packet
loss and general network conditions affecting DNS delivery time.
FWIW, your config has some issues. But nothing that would cause or
related to the problem you are having.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
