HTTP 416 Range Not Satisfiable indicates the Range header in the request specifies a byte range that cannot be fulfilled — typically because the range exceeds the resource's size. The server MUST include a Content-Range header with the actual resource size: Content-Range: bytes */12345. This commonly occurs when a resumed download references a file that has since been truncated or replaced.
Response includes the status code, standard headers (including Content-Type), and a small diagnostic JSON body describing the request and returned status.
Simulator URL (copy in the app after load — not a normal link):
https://httpstatus.com/api/status/416
Example request:
curl -i "https://httpstatus.com/api/status/416"