HTTP 302 Found vs 416 Range Not Satisfiable
HTTP 302 (Found) is a 3xx Redirection response, while 416 (Range Not Satisfiable) is a 4xx Client Error response. 302 indicates that the resource temporarily resides at a different URL. The client should continue using the original URL for future requests. In contrast, 416 means that the server cannot serve the requested byte range. The Range header value is outside the resource's size.
Description
The resource temporarily resides at a different URL. The client should continue using the original URL for future requests.
When You See It
During A/B testing, temporary maintenance pages, or geo-based redirects.
How to Fix
Follow the Location header. Note: browsers may change POST to GET on redirect.
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.
Key Differences
302 is a 3xx Redirection response, while 416 is a 4xx Client Error response.
HTTP 302: The resource temporarily resides at a different URL. The client should continue using the original URL for future requests.
HTTP 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
You encounter 302 when during A/B testing, temporary maintenance pages, or geo-based redirects.
You encounter 416 when when requesting a byte range beyond the file's actual size.
When to Use Which
For 302 (Found): Follow the Location header. Note: browsers may change POST to GET on redirect. For 416 (Range Not Satisfiable): Check the Content-Range in the response for the actual file size and adjust your Range header.