| Previous | Next |
| HTTP_STATUS_UNSUPPORTED_MEDIA | HTTP_STATUS_EXPECTATION_FAILED |
HTTP_STATUS_RANGE_NOT_SATISFIABLE
This commonly occurs when a client resumes a download using an offset beyond the current file length or after the resource changed. The response can include Content-Range: bytes */length to reveal the current length.
Discard stale range metadata, revalidate the resource, and restart or adjust the range. Do not concatenate partial content from different versions of the same resource.
Operational meaning of HTTP 416 for HTTP_STATUS_RANGE_NOT_SATISFIABLE
HTTP 416 (HTTP_STATUS_RANGE_NOT_SATISFIABLE) is a client-error response. AllStat records its meaning as “416 Range Not Satisfiable”. For HTTP_STATUS_RANGE_NOT_SATISFIABLE, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_RANGE_NOT_SATISFIABLE
- Treat HTTP_STATUS_RANGE_NOT_SATISFIABLE as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_RANGE_NOT_SATISFIABLE, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_RANGE_NOT_SATISFIABLE, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For telemetry, record HTTP 416, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.