On 9/06/2015 9:21 a.m., JR Swartz wrote: > We have a customer that uses Squid (3.x). When viewing the > www.fmcdealer.com web site for their business, standard web pages load as > expected. However, when drilling down into the wiring diagrams (which are > in SVG format), there is exactly a 2 minute (120 sec) delay before the > diagrams are displayed. > > > > We've tested this on several svg diagrams and, regardless of the size of the > diagram, the delay is exactly 2 minutes. > > > > Additionally, we've run tcpdump -vv and it appears there is no traffic > during this 2 minute period. > > > > We're hoping someone has seen this or the 120 second delay may trigger > someone's memory about this issue? If the end of the server reply message has not yet been received then this is not a Squid problem. It may be server processing delays, but given that exact timing it is more likely to be a TCP timeout on the connection. If the server emits a message without Content-Length or Transfer-Encoding headers then end-of-message is the TCP connection close signal. If the server fails to close Squid is left waiting for more bytes which will never arrive, until the TCP networking stack times out and closes it. Then Squid relays the end-of-message signal to the client and everything works again. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
