On 10/16/20 11:58 AM, Vieri wrote: > I pinpointed one particular request that's failing: > > 2020/10/16 16:56:37.250 kid1| 85,2| client_side_request.cc(745) clientAccessCheckDone: The request GET https://ed1lncb62601.webex.com/direct?type=websocket&dtype=binary&rand=1602860196950&uuidtag=G7609603-81A2-4B8D-A1C0-C379CC9B12G9&gatewayip=PUB_IPv4_ADDR_2 is ALLOWED; last ACL checked: all > > It is in this log: > > https://drive.google.com/file/d/1OrB42Cvom2PNmV-dnfLVrnMY5IhJkcpS/view?usp=sharing Thank you, that helped a lot! I see that Squid decides that the client has closed the connection. Squid propagates that connection closure to the server. Due to a Squid bug (or my misunderstanding), cache.log does not contain enough details to tell whether the client actually closed the connection in this case and, if it did, whether it did so nicely or due to some TLS error. I filed bug #5084 in hope to improve handling of this case. At the very least, the log should categorize the closure, but it is also possible that the client did not actually close the connection, and Squid is completely mishandling the situation (in addition to being silent about it). See https://bugs.squid-cache.org/show_bug.cgi?id=5084 for details. I cannot volunteer to work on this further right now, but I hope this triage will help another volunteer (or a paid contractor) to make further progress. https://wiki.squid-cache.org/SquidFaq/AboutSquid#How_to_add_a_new_Squid_feature.2C_enhance.2C_of_fix_something.3F Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
