CCloud Releases
Home
Following

Cloud Releases

Service catalogues and updates come from each provider's public product listing and announcements.

Explore

  • Home
  • Latest updates
  • Following

About

  • About
  • Contact
  • Privacy Policy
  • Terms of Use

Providers

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Cloudflare

Not affiliated with any cloud provider. Product names and logos belong to their owners.

  1. Providers
  2. ›Cloudflare
  3. ›Cache / CDN
  4. ›Update

Feature•Sep 2, 2026

Configure Origin Range Requests with the Rulesets API

Cache / CDNCloudflare · Application performance

The Rulesets API now supports Origin Range Requests in Cache Rules. This setting lets Cloudflare fetch large files from your origin in cache-aligned byte ranges. Cloudflare may expand a client range and issue several single-range origin requests.

Set origin_range_requests.mode to on, off, or default for any traffic matched by a Cache Rule.

To override Cloudflare's default Origin Range Requests behavior, set the mode to off. The following rule turns off generated origin range requests for all traffic without changing cache eligibility:

{ "expression": "true", "action": "set_cache_settings", "action_parameters": { "origin_range_requests": { "mode": "off" } } }

Origin Range Requests do not make otherwise ineligible content cacheable. If your origin ignores Range and returns a complete 200 OK, Cloudflare can use the response but must download the complete file. Origins should honor Accept-Encoding: identity and return consistent, unencoded partial responses.

For configuration details and mode behavior, refer to Origin Range Requests in Cache Rules. For client responses and the complete origin contract, refer to Range request behavior.

Read the original announcement↗

More from Cache / CDN

All Cache / CDN updates →
  1. Invalidate cached content instead of purging it

    You can now invalidate cached content instead of purging it. Invalidation marks matching content as stale. On the next request, Cloudflare revalidates the content with your origin.

    Cache / CDN•Feature•Sep 28, 2026
  2. Purge now forces a cache miss for Cache Reserve content

    Purge requests now force a cache miss for Cache Reserve content, regardless of purge type. Previously, purging by cache tag, hostname, prefix, or everything marked matching Cache Reserve content for revalidation.

    Cache / CDN•Feature•Sep 28, 2026
  3. Cache multiple versions of a URL with Vary

    Your origin can serve different responses for the same URL — different languages based on Accept-Language, or different formats based on Accept — by returning a Vary response header.

    Cache / CDN•Feature•Jul 2, 2026
  4. BYPASS status now returned for uncacheable responses

    Cloudflare now returns a BYPASS cache status whenever a response is not cacheable, instead of the previous mix of BYPASS and MISS that depended on why Cloudflare chose not to cache the response.

    Cache / CDN•Feature•May 26, 2026
  5. Pingora now powers Cloudflare's cache

    Cloudflare's cache now runs on a new proxy built on Pingora, the Rust-based framework that already serves a significant portion of Cloudflare's network traffic. The new proxy is faster, more memory-safe, and designed to evolve our cache architecture.

    Cache / CDN•Feature•May 4, 2026