[squid-users] Websockets over HTTPS not working in squid 4

[Felipe Arturo Polanco]

I see.

Are you aware of any unofficial patch or something to tunnel
websockets over HTTPS in squid?



On Thu, Feb 21, 2019 at 5:33 PM Alex Rousskov <
rousskov at measurement-factory.com> wrote:

> On 2/21/19 2:11 PM, Felipe Arturo Polanco wrote:
>
> > I have been trying to make websockets work over HTTPS but so far I
> > haven't been able to.
>
>
> Official Squid cannot reliably detect and proxy native WebSocket
> traffic. Until that support is available, if WebSocket traffic reaches
> your intercepting Squid, then splicing suspected WebSocket connections
> based on TCP/TLS-level information is your only option. And, yes, that
> introduces lots of maintenance headaches, policy violations, and is not
> reliable.
>
> A bit more information about the topic is available on this 2018 thread:
> http://lists.squid-cache.org/pipermail/squid-users/2018-July/018581.html
>
> Alex.
>
>
> > I'm trying the following websites that use websockets and none of them
> work:
> > speedtest.net <http://speedtest.net>
> > web.whatsapp.com <http://web.whatsapp.com>
> > https://slack.com/help/test
> >
> > If I explicitly splice those domain names in squid.conf they work fine.
> >
> > I'm not interested in bumping the websockets, I just want HTTPS
> > interception to work as well as websockets.
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20190221/614dc754/attachment-0001.html>