| Previous | Next |
| HTTP_STATUS_TOKEN_REQUIRED | HTTP_STATUS_SERVER_ERROR |
HTTP_STATUS_CLIENT_CLOSED_REQUEST
The server may have been processing normally when the browser, mobile app, proxy, or network path abandoned the request. It is therefore often a client-side cancellation or an effect of a downstream timeout, not an origin application error.
Compare request duration with client and proxy timeouts, then look for aborts, navigation changes, load-balancer limits, or mobile network interruptions. Do not treat 499 as proof that the server deliberately rejected the request.
NGINX HTTP module documentation
Operational meaning of HTTP 499 for HTTP_STATUS_CLIENT_CLOSED_REQUEST
HTTP 499 (HTTP_STATUS_CLIENT_CLOSED_REQUEST) is a client-error response. AllStat records its meaning as “499 Client Closed Request”. For HTTP_STATUS_CLIENT_CLOSED_REQUEST, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_CLIENT_CLOSED_REQUEST
- Treat HTTP_STATUS_CLIENT_CLOSED_REQUEST as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_CLIENT_CLOSED_REQUEST, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_CLIENT_CLOSED_REQUEST, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For HTTP_STATUS_CLIENT_CLOSED_REQUEST, for telemetry, record HTTP 499, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.