Ugh. Looks like I need to use wss in my environment. I just found this. "If an encrypted WebSocket Secure connection (wss://) is used, then in the case of transparent proxy servers, the browser is unaware of the proxy server, so no HTTPCONNECT is sent. However, since the wire traffic is encrypted, intermediate transparent proxy servers may simply allow the encrypted traffic through, *so there is a much better chance that the WebSocket connection will succeed if an encrypted WebSocket connection is used.*"
Thanks everyone for your help. On Tue, Mar 4, 2014 at 3:50 PM, David kerber <[email protected]> wrote: > On 3/4/2014 3:46 PM, Bob Mancarella wrote: > >> could you try this. >> http://dev.bizunite.com/inlook/echo.html >> >> click on annotation API then Connect and see if you stay connected. >> > > Seems to be working fine for me. > > > > >> >> On Tue, Mar 4, 2014 at 3:44 PM, Mark Thomas <[email protected]> wrote: >> >> On 04/03/2014 20:36, Bob Mancarella wrote: >>> >>>> OK, this is strange. If I go here http://www.websocket.org/echo.html >>>> I get the same results. Click on Connect but don't hit Send and I get a >>>> Disconnected message soon after. >>>> If I use TLS it seems to work. If I hit Send immediately after Connect >>>> it >>>> seems to work. >>>> >>>> Anyone else seeing this? >>>> >>> >>> Not here. >>> >>> Mark >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
