On 11/08/2015 10:07 p.m., Jan Niggemann wrote: > > Hi list, > > first of all: Excuse me if this has been brought up before, but the link > to the search function on page > http://www.squid-cache.org/Support/mailing-lists.html#squid-users > returns a 404. > > Our company introduced a new proxy solution (called Artica). > http://www.lagado.com/proxy-test shows that > "squid/3.5.7-20150801-r13880" is used. > > My problem is that chromium 44 on Win7/64 can't establish a > wss-connection, probably due to incorrect server response headers. I > know for sure that stackoverflow.com handles websockets correctly, but > the server response headers lack 'Connection: Upgrade' and show > 'Connection: keep-alive" instead. A screenshot and debug log is > available in my question on SO: > http://stackoverflow.com/questions/31935536/make-chromium-use-connect-for-websockets > > > Is there a squid setting that I need to tell our administrators about, > so websocket connections will work? Squid simply does not support HTTP Upgrade yet. To anything. Chromium is requesting a GET with _optional_ Upgrade to WebSockets, OR a fallback of HTTP/1.1. Since Squid does not Upgrade the HTTP/1.1 fallback is used. The response headers are correctly signalling that HTTP was used instead of WebSockets. There is nothing we can do if the client software actively offers to accept a fallback that it does not support. Chromium (or anything) should still be able to use HTTP CONNECT tunnels to perform WebSockets through Squid. Maybe it just needs to be aware of the proxies existence (non-MITM). Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
