ws: Connection stuck in CLOSING state

Probably it starts with some connection problem: readyState is set to 2 (CLOSING) and close event is never fired. Is this expected?

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 2
Comments: 22 (9 by maintainers)

Commits related to this issue

Add flag in debug client to print connection closed message only once WebSocketServer close method send a close frame first, then it sends a FIN packet, so, as an outcome WebSocket close event is fir... — committed to eclipsesource/tabris-js-cli by ahmadov 6 years ago

Most upvoted comments

I’ll try to collect some more details then.

+1

zdila on May 26, 2017

Read more comments on GitHub

← ws: Connect to websocket under cloudflare causes 403 forbidden error

ws: ERROR Invalid WebSocket frame: invalid status code 22373 →