Origin Range Requests: Serving large files without range-request tuning
Web page · https://blog.cloudflare.com/origin-range-requests
Naive byte-range caching can waste gigabytes of origin bandwidth on small requests. We rebuilt our cache architecture in Pingora to coordinate partial fetches automatically, cutting R2 p99 latency in half.
First seen by Oriel on .
AI summary
Cloudflare’s Origin Range Requests replaces customer-configured range sizes with cache-chunk-aligned origin fetches, reducing wasted transfers while coordinating cached, in-flight, and newly fetched bytes.
- The feature is enabled for matching traffic through a Cache Rule and is available on all plans without range-size tuning.
- Cloudflare serves cached bytes directly, fetches missing bytes in fixed-size chunk-aligned ranges, and returns only the client-requested bytes.
- Concurrent requests can share in-flight downloads, while validators and range checks prevent composing bytes from different representations.
- For R2, p99 time to first byte fell by roughly half, and tiered cache traffic for R2 and similar workloads dropped about 6% week over week.
- The feature does not make uncacheable responses cacheable, and useful partial origin fetches require the origin to support byte ranges.
#cloudflare #http range requests #cdn caching #r2
Generated by gpt-5.6-sol. Check the original for details.
Aliases
| Source | External ID | URL |
|---|---|---|
| Cloudflare Blog | 01M5MZPETYH27RS72QV5V85YZ8 | https://blog.cloudflare.com/origin-range-requests/ Read discussion |