On Saturday, October 17, 2020, 10:36:47 PM GMT+2, Alex Rousskov <rouss...@measurement-factory.com> wrote:
> or due to some TLS error. > I filed bug #5084 Hi again, Thanks for opening a bug report. I don't want to add anything there myself because I wouldn't want to confuse whoever might take this issue into account, but I'd like to comment on this list that I've captured the traffic between Squid and the destination server. It's here: https://drive.google.com/file/d/1WS7Y62Fng5ggXryzKGW1JOsJ16cyR0mg/view?usp=sharing I can see a client hello, Server Hello Done, Cipher Spec, etc, but then it starts over and over again. So, could it be a TLS issue as you hinted? I also captured the client console regarding the wss messages (Firefox). It won't reveal much, but here it is anyway: https://drive.google.com/file/d/1u4uXW0TCTwClE2kt2nbJSGt5VLdKC03t/view?usp=sharing NB: the destination server is not the same one as in the packet trace, but that's what the client gets each time (it keeps showing '101 Switching Protocols' over and over). Please let me know if I should add something to the bug report, or if you see anything of interest in the data I've sent. Thanks, Vieri _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
