mrjoes
commented
11 years ago Did you try terminating SSL before sockjs-node server? For example, at load balancer (haproxy/nginx with websocket support)?
Also, can you see what was the closing frame code by capturing some traffic?
P.S. If it is Windows Azure, is it Windows host, not Linux host? I think there was load balancer from Microsoft that supports SSL termination and websockets.
Serge.
On Wed, Jun 19, 2013 at 10:00 AM, Aaron notifications@github.com wrote:
We have a SockJs client app that connects to a SockJs Node server (hosted in Windows Azure). Recently we completed the update on the server side to support SSL. So our client now connects with to a URL like https://socketservice.cloudapp.net.
For most part that works totally fine. But every now and then, we see Google Chrome lose connectivity, something we've never seen before when using http
WebSocket connection to 'wss:// socketservice.cloudapp.net/socket/650/pfz10b/websocket' failed: Received a broken close frame containing a reserved status code.
The problem will persist for a period of time, and then disappear all by itself; the client can then connect and work again.
That particular error message seems to be a very specific webkit error message, and pages discussing that involve webkit source code that is beyond my understanding. It seems that Chrome got a close frame from the server which is not of an expected close status code. However I still do not understand enough of the Websocket protocol to figure out who initiated the close, why there is even a close (when they are suppose to maintain a connection), and which software layer needs troubleshooting.
The server side Node implementation certainly does not actively close any connections. It just listens on client connection, data, and close events.
Would like to know where we should focus our further troubleshooting effort to understand the root cause of this. thanks.
— Reply to this email directly or view it on GitHubhttps://github.com/sockjs/sockjs-client/issues/122 .
icelava
majek
We have a SockJs client app that connects to a SockJs Node server (hosted in Windows Azure). Recently we completed the update on the server side to support SSL. So our client now connects with to a URL like https://socketservice.cloudapp.net.
For most part that works totally fine. But every now and then, we see Google Chrome lose connectivity, something we've never seen before when using http
WebSocket connection to 'wss://socketservice.cloudapp.net/socket/650/pfz10b/websocket' failed: Received a broken close frame containing a reserved status code.
The problem will persist for a period of time, and then disappear all by itself; the client can then connect and work again.
That particular error message seems to be a very specific webkit error message, and pages discussing that involve webkit source code that is beyond my understanding. It seems that Chrome got a close frame from the server which is not of an expected close status code. However I still do not understand enough of the Websocket protocol to figure out who initiated the close, why there is even a close (when they are suppose to maintain a connection), and which software layer needs troubleshooting.
The server side Node implementation certainly does not actively close any connections. It just listens on client connection, data, and close events.
Would like to know where we should focus our further troubleshooting effort to understand the root cause of this. thanks.