1005
No Status Received
Sent by: ReservedRetryable
1005 No Status Received is a reserved code used internally by WebSocket libraries to indicate the TCP connection was closed without a WebSocket close frame. It is never sent in an actual close frame – it is a pseudo-code that client libraries return to application code when the connection drops without a clean close handshake.
Description
1005 is never transmitted over the wire. It is generated by WebSocket libraries when the underlying TCP connection closes but no WebSocket close frame was received. This can happen when a server crashes, a network drops mid-connection, or a proxy closes the TCP connection. Application code receiving 1005 should attempt to reconnect.
Common Causes
- –Server crashed without sending close frame
- –Network connection dropped
- –Proxy closed TCP connection without WebSocket close handshake
- –Container or process killed with SIGKILL
Code
1005
RFC
RFC 6455
Sent By
Reserved
Retry
Yes