Indicates the reason why a websocket connection is beingg closed.
| Member Name | Description |
|---|---|
| AbnormalClosure | The connection was closed abnormally - probably due to an exception being thrown somewhere. |
| CloseReasonLost | The close reason sent or received has been lost somehow - probably due to garbage collection. |
| ExtensionsNotPresent | One or more required extensions weren't negotiated in the initial handshake. |
| FrameTooBig | A frame was received that's too big for the receiving party to process. |
| InconsistentDataEncoding | A text message was received that doesn't match the encoding that it claims to be written in. |
| Normal | The connection was closed normally. |
| NoStatusCodePresent | No status code was specified. |
| NotAcceptableDataType | An involved party didn't like the type of frame sent by the other party. |
| NotClosedYet | The connection hasn't closed yet. You shouldn't ever see this status code when a connection has been closed! If you do, then it means there's a _bug_. |
| PolicyViolation | A generic code for when a message sent by the other party violates the receiving party's policy. |
| ProtocolError | An involved party had an issue with the syntax of a message they received from the other party. |
| Reserved | A reserved close code. Should not be used. |
| Shutdown | The connection was closed because either or both parties are shutting down / going away. |
| TlsHandshakeFailure | The TLS handshake failed. This _shouldn't_ be actually sent to the client - it's for logging purposes only. |
| UnexpectedCondition | The server has encountered an 'unexpected' condition that is preventing it from fulfilling the request in the frame received. |