case normalClosure
Indicates a normal closure, meaning that the purpose for which the connection was established has been fulfilled. Corresponds to code 1000.
case goingAway
Indicates that an endpoint is “going away”, such as a server going down or a browser having navigated away from a page. Corresponds to code 1001.
case protocolError
Indicates that an endpoint is terminating the connection due to a protocol error. Corresponds to code 1002.
case unacceptableData
Indicates that an endpoint is terminating the connection because it has received a type of data it cannot accept (e.g. an endpoint that understands only text data may send this if it receives a binary message). Corresponds to code 1003.
case dataInconsistentWithMessage
Indicates that an endpoint is terminating the connection because it has received data within a message that was not consistent with the type of the message (e.g. non-UTF-8 data within a text message). Corresponds to code 1007.
case policyViolation
Indicates that an endpoint is terminating the connection because it has received a message that violates its policy. This is a generic status code that can be returned when there is no other more suitable status code (e.g. 1003 or 1009) or if there is a need to hide specific details about the policy. Corresponds to code 1008.
case messageTooLarge
Indicates that an endpoint is terminating the connection because it has received a message that is too big for it to process. Corresponds to code 1009.
case unexpectedServerError
Indicates that a server is terminating the connection because it encountered an unexpected condition that prevented it from fulfilling the request. Corresponds to code 1011.
case unknown(UInt16)
We don’t have a better name for this error code.