416 Range Not Satisfiable

The byte range asked for is outside the file.

Code: 416
Reason phrase: Range Not Satisfiable
Class: 4xx Client error
Defined in: RFC 9110 section 15.5.17
Cacheable by default: No

What it means

Client error: the problem lies with the request. Repeating it unchanged will normally fail again.

Common causes. Resuming a download of a file that has since changed or shrunk.

What to do. Restart the download from the beginning.

How clients and crawlers treat it

Google Search. Like every 4xx except 429, it tells Google the content does not exist: an indexed URL is removed from the index, and a new one is not processed. Crawl frequency for the URL gradually drops. Source: Google Search Central, How HTTP status codes, and network and DNS errors affect Google Search.

Caching. Not cacheable by default (RFC 9110 section 15.1 does not list it). A cache stores it only when the response says so with Cache-Control or Expires.

Example response

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

Range Not Satisfiable

How to send 416

nginx

location /example {
    return 416;
}

Apache (.htaccess)

RewriteEngine On
RewriteRule ^example$ - [R=416,L]

PHP

http_response_code(416);
echo 'Range Not Satisfiable';
exit;

Node.js

res.writeHead(416, { 'Content-Type': 'text/plain' });
res.end('Range Not Satisfiable');

Python (Flask)

# in a view function
return 'Range Not Satisfiable', 416

Change the paths to suit. In nginx, add_header needs always to apply to error responses.

Related codes

All status codes · All 4xx codes

Names and numbers from the IANA HTTP Status Code Registry. Google Search behaviour as documented by Google Search Central.