WebSocket 1001 Going Away vs 1013 Try Again Later
Both WebSocket 1001 (Going Away) and 1013 (Try Again Later) 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, 1013 means that the server is terminating the connection due to a temporary condition, such as being overloaded. The client should reconnect after a back-off period.
Описание
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.
Описание
The server is terminating the connection due to a temporary condition, such as being overloaded. The client should reconnect after a back-off period.
Когда вы это видите
The server is temporarily overloaded or throttling connections. Unlike 1012, this does not indicate a restart — the server is running but cannot serve more clients right now.
Как исправить
Reconnect using exponential backoff (start at 1 second, double each attempt). If persistent, investigate server capacity, scale horizontally, or reduce the number of concurrent connections.
Ключевые различия
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 1013: The server is terminating the connection due to a temporary condition, such as being overloaded. The client should reconnect after a back-off period.
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 1013 when the server is temporarily overloaded or throttling connections. Unlike 1012, this does not indicate a restart — the server is running but cannot serve more clients right now.
Когда что использовать
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 1013 (Try Again Later): Reconnect using exponential backoff (start at 1 second, double each attempt). If persistent, investigate server capacity, scale horizontally, or reduce the number of concurrent connections.