Non-standard, from nginx: the client closed the connection before the server sent a response. nginx writes it to the access log; no client ever receives it over the wire.
Non-standard — not defined by any RFC. Vendor documentation: nginx source — NGX_HTTP_CLIENT_CLOSED_REQUEST
In nginx access logs, next to requests from mobile clients on flaky networks, from load balancers with short health-check timeouts, and from browsers whose users navigated away. It shows up most around slow endpoints, because those are the requests clients give up on.
Useful for testing log parsing and dashboards, and as a reminder that a client-side timeout leaves a 499 behind on the server — the request may still have run to completion.
There is nothing to handle on the client: by definition the client already left. On the server, read a rise in 499s as "clients time out before we answer" — compare the endpoint's latency with the client timeouts and decide which one to move. Remember the work may have completed anyway, so retries need idempotency.
1 endpoint in this playground answers with 499. Every one is free, needs no signup, and can be called from the browser or with curl.
GET https://funapi.dev/api/faults/v1/status/{code} — Return any status code on demand (200–599) (Fault Injection API) Open & run this endpointAll HTTP status codes · All 55 mock REST APIs · Getting started guide
Last updated