Chrome : websocket connection not closed when browser closed

google-chrome websocket netty
Rndm picture Rndm · Aug 1, 2012 · Viewed 7.8k times · Source

I am using Netty websockets and everything seems to work fine except this minor issue :

If I close the browser / tab of the js websocket client , the websocket connection is automatcally closed when using Mozilla firefox (currently using firefox 14) but the same thing does not happen in Chrome 20/21.

Anyone seen a similar issue / can anyone tell why is the connection not closed automatically ?

Answer

Rndm picture Rndm · Aug 2, 2012

I guess I should have checked this earlier in the chromium bug section but I was not sure if it is a bug. It has been reported earlier by someone and a chromium bug already exists :

Issue 51687 : WebSocket: Send close with code 1001 on reload / tab close

Update : Someone has submitted a patch to fix this issue, can be seen in the above link.

Related questions

Debugging WebSocket in Google Chrome

Is there a way, or an extension, that lets me watch the "traffic" going through a WebSocket? For debugging purposes I'd like to see the client and server requests/responses.

Read More
Differences between socket.io and websockets

What are the differences between socket.io and websockets in node.js? Are they both server push technologies? The only differences I felt was, socket.io allowed me to send/emit messages by specifying an event name. In the case …

Read More
websocket closing connection automatically

I'm building an application in java that has an embedded websocket server based on jetty. The client is the default websocket implementation in google chrome. Everything is working ok, only if there is no transfer between server and client after …

Read More