| 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.
Correlate client and upstream timing
A 499 entry often means the upstream application was still working when the browser, API client, load balancer, or another intermediary abandoned the request. Correlate client timeout settings with NGINX request time and upstream timing. A slow origin can therefore produce many 499 log entries even though NGINX itself did not reject the requests.
Looking for a different code? Search another status or error code.
