ConstReserved. Emitted when connection was closed abnormally, where status code was expected.
Emitted when endpoint is going away, e.g. on navigation or server failure.
Indicates that server received a message with inconsistent data structure, e.g. a mixed UTF-8 encoded message that also includes the unrecognizable binary data.
Indicates that received payload by the server is too large to be processed.
Reserved. Indicates lack of the status/code, although it was expected.
Indicates that connection went successfully.
Indicates that sent message violates the server's policy. This code is meant to be a generic status code that can be used if there's no suitable more suitable status codes (like UnsupportedData or MessageTooBig). It could also be used if details about the policy should be hidden.
Emitted once a protocol error occurs.
Reserved. It currently has no meaning, but that might change in the future.
Emitted when server is terminating connection due to the temporarily condition, e.g. server overload.
Emitted once server received a kind of data it couldn't accept, e.g. binary message on endpoints supporting only UTF-8 encoded data.
A list of standard status codes used within WebSocket communication at connection close. Currently, not all are documented there, although all were listed, with some additional ones took from MDN.
Reference: MDN, RFC 6455.