Skip to main content
apiguide.dev

Content-Range Header

Indicates which portion of a resource is delivered in a partial response.

Header TypeResponse Header
SpecificationStandard RFC compliant
Associated CodesHTTP 206,HTTP 416

What is the Content-Range header?

The Content-Range response header describes where a returned chunk of data fits within the complete resource. It accompanies a 206 Partial Content response and states the byte range being sent along with the total size of the full representation.

API Usage & Best Practices

  • Reassembling downloads: Clients use the range and total-length values to place each chunk correctly and to know when the whole resource has been received.
  • Signalling unsatisfiable ranges: In a 416 Range Not Satisfiable response, Content-Range: bytes */146515 reports the total size so the client can retry with a valid range.

Examples

HTTP/1.1 206 Partial Content
Content-Range: bytes 0-1023/146515
Content-Length: 1024

Associated HTTP Status Codes

HTTP 206 — Partial Content

The server is delivering only part of the resource due to a Range header sent by the client.

View reference →

HTTP 416 — Range Not Satisfiable

The requested byte range cannot be satisfied by the server.

View reference →

Sponsors

Support the project →