Navigation
Introduction
HTTP Status Code 416- requested range not satisfiable is one of the classes of 4xx(Server Error) response code that indicates the server is unable to serve the requested ranges.
The most likely explanation is that the document lacks such ranges, or that the Range header value, while syntactically accurate, makes no sense.
General Understanding
It’s feasible for a client to ask a server for partial replies. A customer may simply want the first 5 minutes of a movie or the last 100 lines of a log file, for example.
With range requests, HTTP clients and servers may achieve this.
This request, for example, requests the first 100 bytes:
| GET /foo.md HTTP/1.1 Range: bytes=1-100 |
If a server does not support range requests, it will respond with 200 OK, and the whole resource will be returned. If range requests are supported, it can utilize 206 Partial Content to deliver exactly what the client requested.
If a client requests a range that doesn’t make sense, 416 Range Not Satisfiable might be used to communicate this. For instance, suppose a file had 1024 bytes in size and the client requested bytes 2000-3000.
| HTTP/1.1 416 Range Not Satisfiable Content-Range: bytes */1000 |
Status
| 416 Range Not Satisfiable |
Causes
It’s possible that the problem is caused by your browser caching the original CSS files and attempting to request byte ranges from the new ones. Take, for example, this Chrome problem.
If you delete your browser cache, you might not need to disable range requests, but if you must, you could use the following Apache config:
| Header unset Accept-Ranges |
This informs clients that they are unable to request byte ranges of your files using the Range request header.
How Do I Fix 416 Range Not Satisfiable issues ?
We can fix HTTP Status Code 416 Issues by following wages:
| 1. Reinstalling the package 2. Clear caching |
Specifications
| Specification | Title |
| RFC 7233, section 4.4: 416 Request Not Satisfiable | Hypertext Transfer Protocol (HTTP/1.1): Range Requests |
Related Articles
| HTTP Status Code 207 Multi-Status |
| HTTP Status Code 300-Multiple Choices |
| HTTP Status Code 302 Found |
| HTTP Status Code 204 – No Content |
FAQ
What does HTTP Status Code 416 mean?
HTTP Status Code 416- requested range not satisfiable is one of the classes of 4xx(Server Error) response code that indicates the server is unable to serve the requested ranges.
What are the causes of HTTP Status Code Error 416?
Requested Range Not Satisfiable is caused by your browser caching the original CSS files and attempting to request byte ranges from the new ones.
It’s possible that the problem is caused by your browser caching the original CSS files and attempting to request byte ranges from the new ones. Take, for example, this Chrome problem.
If you delete your browser cache, you might not need to disable range requests, but if you must, you could use the following Apache config:
Header unset Accept-Ranges
This informs clients that they are unable to request byte ranges of your files using the Range request header.
How to fix 416 Range Not Satisfiable issues?
We can fix HTTP Status Code 416 Issues by following wages:
1. Reinstalling the package.
2. Clear caching
Conclusion
That should cover all the bases when it comes to the 416 requested range, not satisfiable issues. While there isn’t always much you can do when you get a 506 error, maybe some of these tips will come in handy the next time you get one.
I hope this article was able to help you with your doubts and queries related to the HTTP status code 416 Requested Range Not Satisfiable.
Still, if there are any queries related to this topic, feel free to ask in the comment section, we would be happy to assist you. Thank you.
Saurabh Chalise