HTTP 416 – Range Not Satisfiable
The range specified by the Range header cannot be fulfilled.
Common use case
Returned when a download manager or video player requests a byte range that falls outside the actual size of the file, e.g. after the file was replaced with a smaller one.
Example
HTTP/1.1 416 Range Not Satisfiable
Content-Range: bytes */1000
History
Originally named "Requested Range Not Satisfiable" in HTTP/1.1 (RFC 2068, 1997); shortened in RFC 7233 (2014).
Did you know?
It is the 206 Partial Content code's error-case counterpart - wherever range requests are supported, this is the code that guards against invalid ranges.