416 Range Not Satisfiable
This is an educational reference page about HTTP 416 Range Not Satisfiable. The page itself is served as 200 OK so it can be indexed as HTTP documentation.
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called "Requested Range Not Satisfiable" previously.
Specification
Registered in the IANA HTTP Status Code Registry as Range Not Satisfiable. Defined in RFC 9110, Section 15.5.17.
Header and content rules
What RFC 9110 says about a 416 response, quoted from the RFC. The 4xx class rules also apply.
- SHOULD (server; Content-Range): Send Content-Range with the current length, for example bytes */47022. When: The request was a byte-range request. Table row
A server that generates a 416 response to a byte-range request SHOULD generate a Content-Range header field specifying the current length of the selected representation (Section 14.4). RFC 9110 §15.5.17
The same rule is in the response obligations table and its JSON.