You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Bug
When the javascript client tries to close the connection, the close process does not complete cleanly, and often waits for a timeout. This is because the server is not sending back the web socket close FIN message. It is supposed to work as follows:
Client.close() -> Web Socket Close [code, message] -> Server -> Server Close Event Fired
|
Client <- Web Socket Close[same code, same message] <--|
|
|--> Client Close Event Fired
Without the server sending the TCP FIN message back to the client, the client will wait until whatever timeout the specific implementation provides. This often results in a protracted delay, as well as an error event being emitted.
Expected Behavior
The server should properly complete the close request.
The text was updated successfully, but these errors were encountered:
Versions
Describe the Bug
When the javascript client tries to close the connection, the close process does not complete cleanly, and often waits for a timeout. This is because the server is not sending back the web socket close FIN message. It is supposed to work as follows:
Without the server sending the TCP FIN message back to the client, the client will wait until whatever timeout the specific implementation provides. This often results in a protracted delay, as well as an error event being emitted.
Expected Behavior
The server should properly complete the close request.
The text was updated successfully, but these errors were encountered: