Skip to the content

416 Range Not Satisfiable

The Range header asks for a part of the file that doesn't exist, such as bytes beyond its end.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110
Also known as
Requested Range Not Satisfiable

What it looks like

HTTP/1.1 416 Range Not Satisfiable
Content-Range: bytes */1000

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When none of the ranges in the request overlaps the resource. The typical case is a download that resumes at a position past the end of the file, because the file on the server became shorter or the half-finished file on disk belongs to another version. The response gives the real length in Content-Range.

What to do about it

Start from the beginning: delete the partial download and fetch the whole file.

If your own code builds the Range header, remember that positions count from 0, so the last byte of a file of 1,000 bytes is number 999. Asking to resume exactly at the end, with bytes=1000-, gets a 416, which is how a client can tell that the download was complete already.

Not to be confused with

206 Partial ContentThe range exists and is sent.
200 OKThe server ignores ranges and sends the whole file.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12