A 416 Range Not Satisfiable error occurs when the client sends a request containing a Range header field, but none of the ranges requested overlap the current extent of the selected resource.
Browsers and media players use byte ranges (e.g., Range: bytes=5000-10000) to stream video, stream audio, or resume interrupted downloads without re-downloading the entire file from the beginning.
Determining why
If a client asks for bytes 1000 to 2000 of a file that is only 500 bytes long, the server cannot fulfill that range and returns a 416 response accompanied by a Content-Range header indicating the actual size of the file.
Steps you could possibly take:
- Clear your browser’s download cache - Interrupted download managers sometimes attempt to resume a download using outdated byte offsets after a file on the server was replaced with a smaller version.
- Restart the download from scratch - Delete the partial temporary file and initiate a clean download.
- If you are a developer - Check your client’s byte range arithmetic to ensure the requested start and end offsets are within the target file’s total byte boundary.