4xx Client Error
Not part of the HTTP standard
499 Client Closed Request
Non-standard nginx code: the client disconnected before the server replied.
What causes it
- A user navigated away or hit stop while a slow request was in flight.
- A load balancer or client library timeout shorter than the server response time.
- A mobile client losing connectivity mid-request.
How to fix it
- Usually harmless if occasional. A spike means your responses are slower than your clients are willing to wait — compare `upstream_response_time` with the client timeout.
At a glance
- Class
- 4xx Client Error
- Reference
- nginx (non-standard)
- Standardised
- No — vendor extension
- Retry the request?
- No — fix the request
Other 4xx client error codes
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Content Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 417 Expectation Failed
- 418 I'm a teapot
- 421 Misdirected Request
- 422 Unprocessable Content
- 423 Locked
- 424 Failed Dependency
- 425 Too Early
- 426 Upgrade Required
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons