What is 206 partial content range requests?

Pass-through: CDN forwards the Range header to the origin, caches the partial response. Subsequent range requests for the same bytes are served from cache.
Full-object caching: CDN fetches the entire object from the origin, caches it, and serves ranges from the cached full object. More efficient for resources with many different range requests.
Slice: CDN breaks the object into fixed-size slices (e.g., 1MB each), fetches and caches slices independently. Cloudflare, AWS CloudFront, and Akamai support this.

Understanding HTTP 206 Partial Content for Range Requests is a common topic when working with HTTP and APIs. Understanding it helps you diagnose issues and choose the right status codes and headers. Use our Header Inspector and AI Inspector to analyze your requests and responses.

How can I debug 206 partial content range requests?

Use the Header Inspector to inspect request and response headers, the Status Analyzer to send live requests, and the AI Inspector to get recommendations. Check the Knowledge Center for more guides.

Which tools on HttpStatus.com help with 206 partial content range requests?

Header Inspector, Redirect Checker, AI Inspector, and the API Client are useful. Visit the relevant hub (e.g. CORS Hub, Redirect Hub) for more tools and references.

Where can I learn more about HTTP status codes?

Visit the Status codes reference and the HTTP Hub on HttpStatus.com for full documentation and interactive tools.

Understanding HTTP 206 Partial Content for Range Requests