HTTP 416 Range Not Satisfiable vs 425 Too Early
Both HTTP 416 (Range Not Satisfiable) and 425 (Too Early) 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, 425 means that the server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
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 is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
When You See It
When a server rejects a request sent as TLS 1.3 early data due to replay risk.
How to Fix
Retry the request after the TLS handshake completes.
Key Differences
HTTP 416: The server cannot serve the requested byte range. The Range header value is outside the resource's size.
HTTP 425: The server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
You encounter 416 when when requesting a byte range beyond the file's actual size.
You encounter 425 when when a server rejects a request sent as TLS 1.3 early data due to replay risk.
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 425 (Too Early): Retry the request after the TLS handshake completes.