Enum CentrifugeCloseCode#

Close code not set

The connection successfully completed the purpose for which it was created.

The endpoint is going away, either because of a server failure or because the browser is navigating away from the page that opened the connection.

The endpoint is terminating the connection due to a protocol error.

The connection is being terminated because the endpoint received data of a type it cannot accept. (For example, a text-only endpoint received binary data.)

Reserved. A meaning might be defined in the future.

Reserved. Indicates that no status code was provided even though one was expected.

Reserved. Indicates that a connection was closed abnormally (that is, with no close frame being sent) when a status code is expected.

The endpoint is terminating the connection because a message was received that contained inconsistent data (e.g., non-UTF-8 data within a text message).

The endpoint is terminating the connection because it received a message that violates its policy. This is a generic status code, used when codes 1003 and 1009 are not suitable.

The endpoint is terminating the connection because a data frame was received that is too large.

The client is terminating the connection because it expected the server to negotiate one or more extension, but the server didn't.

The server is terminating the connection because it encountered an unexpected condition that prevented it from fulfilling the request.

Reserved. Indicates that the connection was closed due to a failure to perform a TLS handshake (e.g., the server certificate can't be verified).

is clean disconnect when client cleanly closed connection.

sent when node is going to shut down.

sent when client came with invalid token.

sent when client uses malformed protocol frames or wrong order of commands.

sent when internal error occurred on server.

sent when client connection expired.

sent when client subscription expired.

sent to close connection that did not become authenticated in configured interval after dialing.

sent when client can't read messages fast enough.

sent when an error occurred while writing to client connection.

sent when server detects wrong client position in channel Publication stream. Disconnect allows client to restore missed publications on reconnect.

sent when server disconnects connection.

sent when server disconnects connection and asks it to not reconnect again.

can be sent when client connection exceeds configured connection limit (per user ID or due to other rule).

can be sent when client connection exceeds configured channel limit.