416 Range Not Satisfiable
4xx client error
The requested byte range cannot be fulfilled, usually because it starts beyond the current resource length, and the server reports the actual size.
Common causes
- A resume request for bytes past the end of a truncated file.
- A stale range from a cached manifest after the file shrank.
- A malformed Range header with an impossible start offset.
How to fix it
- Return Content-Range with the current full size so clients can restart.
- Invalidate cached manifests when the file size changes.
- Handle suffix and open-ended ranges correctly.
What it means for redirects and SEO
Broken range requests break resumable downloads and media playback. Mismatched range caching is typical. Report the current size in Content-Range.