WebSocket Status Codes
A protocol providing full-duplex communication channels over a single TCP connection. Close codes indicate why a connection was terminated.
View Specification →1000-1015 WebSocket Close Codes
IANA-registered WebSocket close status codes (RFC 6455).
The connection has been closed normally. Both endpoints consider the session complete.
An endpoint is going away (e.g., server shutting down or browser navigating away).
An endpoint is terminating the connection due to a protocol error.
An endpoint received a type of data it cannot accept (e.g., text-only got binary).
Reserved. Indicates that no status code was present. Must not be sent in a Close frame.
Reserved. Indicates the connection was closed abnormally (no Close frame sent).
An endpoint received data that was inconsistent with the message type (e.g., non-UTF-8 in text).
An endpoint received a message that violates its policy.
An endpoint received a message that is too large to process.
The client expected the server to negotiate a required extension.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server is restarting. The client may reconnect.
The server is temporarily overloaded. The client should reconnect later.
The server acting as gateway received an invalid response from the upstream server.
Reserved. Indicates failure to perform TLS handshake. Must not be sent in a Close frame.