HTTP 416 Range Not Satisfiable vs 502 Bad Gateway
HTTP 416 (Range Not Satisfiable) is a 4xx Client Error response, while 502 (Bad Gateway) is a 5xx Server Error response. 416 indicates that the server cannot serve the requested byte range. The Range header value is outside the resource's size. In contrast, 502 means that the server, acting as a gateway or proxy, received an invalid response from the upstream server.
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
The server, acting as a gateway or proxy, received an invalid response from the upstream server.
When You See It
When Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
How to Fix
Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.
Key Differences
416 is a 4xx Client Error response, while 502 is a 5xx Server Error response.
HTTP 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
HTTP 502: The server, acting as a gateway or proxy, received an invalid response from the upstream server.
You encounter 416 when when requesting a byte range beyond the file's actual size.
You encounter 502 when when Nginx/Apache can't reach the application server (e.g., Gunicorn is down, upstream timeout).
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 502 (Bad Gateway): Check if the upstream server is running. Verify proxy configuration. Check for upstream timeouts.