HTTP 416 Range Not Satisfiable vs 499 Client Closed Request
Both HTTP 416 (Range Not Satisfiable) and 499 (Client Closed Request) belong to the 4xx Client Error category. 416 indicates that the server cannot serve the requested byte range. The Range header value is outside the resource's size. Meanwhile, 499 means that a non-standard status code used by Nginx when the client closes the connection before the server responds.
Description
The server cannot serve the requested byte range. The Range header value is outside the resource's size.
When You See It
When requesting a byte range beyond the file's actual size.
How to Fix
Check the Content-Range in the response for the actual file size and adjust your Range header.
Description
A non-standard status code used by Nginx when the client closes the connection before the server responds.
When You See It
In Nginx logs when clients timeout or navigate away before receiving the response.
How to Fix
Optimize server response times. Check for slow upstream services.
Key Differences
HTTP 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
HTTP 499: A non-standard status code used by Nginx when the client closes the connection before the server responds.
You encounter 416 when when requesting a byte range beyond the file's actual size.
You encounter 499 when in Nginx logs when clients timeout or navigate away before receiving the response.
When to Use Which
For 416 (Range Not Satisfiable): Check the Content-Range in the response for the actual file size and adjust your Range header. For 499 (Client Closed Request): Optimize server response times. Check for slow upstream services.