WebSocket 1001 Going Away vs 1009 Message Too Big
Both WebSocket 1001 (Going Away) and 1009 (Message Too Big) belong to the WebSocket Close Codes category. 1001 indicates that an endpoint is going away, such as a server shutting down or a browser navigating away from the page. The connection must be closed. Meanwhile, 1009 means that an endpoint is terminating the connection because it received a message that is too large for it to process.
説明
An endpoint is going away, such as a server shutting down or a browser navigating away from the page. The connection must be closed.
このコードが表示される場合
The server is shutting down for maintenance, or the user navigated away from the page or closed the browser tab while a WebSocket was open.
解決方法
Implement automatic reconnection logic with exponential backoff in your client. If the server is restarting, the client should retry after a short delay.
説明
An endpoint is terminating the connection because it received a message that is too large for it to process.
このコードが表示される場合
The message payload exceeded the server's configured maximum frame or message size limit. Common when uploading large files or sending huge JSON payloads over WebSocket.
解決方法
Reduce the message size by chunking large payloads into smaller frames. Alternatively, increase the server's max message size configuration if the large payload is expected.
主な違い
WebSocket 1001: An endpoint is going away, such as a server shutting down or a browser navigating away from the page. The connection must be closed.
WebSocket 1009: An endpoint is terminating the connection because it received a message that is too large for it to process.
You encounter 1001 when the server is shutting down for maintenance, or the user navigated away from the page or closed the browser tab while a WebSocket was open.
You encounter 1009 when the message payload exceeded the server's configured maximum frame or message size limit. Common when uploading large files or sending huge JSON payloads over WebSocket.
どちらをいつ使うか
For 1001 (Going Away): Implement automatic reconnection logic with exponential backoff in your client. If the server is restarting, the client should retry after a short delay. For 1009 (Message Too Big): Reduce the message size by chunking large payloads into smaller frames. Alternatively, increase the server's max message size configuration if the large payload is expected.