Cloudflare's Cache Rules have reached general availability, roughly a year after the product entered beta in late September 2022. More than 100,000 websites already use the feature, which lets customers shape caching behavior through a rules-based interface without writing code. Several other Rules products are going GA alongside it, and the release adds new configuration options on top of the existing ones.
What ships with the GA release
The newly introduced configuration levers cover four areas: deciding which resources are eligible for Cache Reserve, setting the timeout values honored while receiving data from an origin, choosing which custom ports Cloudflare uses when caching content, and specifying whether Cloudflare should bypass its cache when no cache-control header is present.
Existing behavior is unchanged in its fundamentals. Cache Rules work like other ruleset engine products: user-defined criteria such as URLs or request headers are evaluated, and when they match, the specified cache configuration is applied. Each rule is built from fields, operators and values.
Why Page Rules needed a successor
Cache customization on Cloudflare dates back to Page Rules, a product that became the default way to exercise granular control over caching. More than 5 million cache-related Page Rules are currently active. Behind the scenes, though, Page Rules carried a structural limit.
Every Page Rule encountered is transformed into a single regex pattern combining all of a customer's conditions, and that pattern is then applied to requests. Against tens of millions of requests per second across more than 300 data centers, the computational cost is substantial, and that cost capped how many rules a single website could deploy: Page Rules allow only 125 per site.
Rebuilding the functionality on the Rulesets Engine removed that constraint. Rather than collapsing all rules into one regular expression, ruleset engine products evaluate rule logic conditionally — a request from subdomain A can be matched using only the logic that applies to A, skipping anything defined for subdomain B. Fewer computations per request follow, and users get more rules and more flexibility about when rules run.
Cache Rules, together with Origin Rules, Configuration Rules and Single Redirect Rules, has spent the past year in beta. The company says the quartet now covers everything Page Rules could do and more, and that Page Rules has entered its end-of-life process. Timelines and migration details will be announced in the coming months; the transition is to be automated as far as possible with simple steps for customers.
Two strategies in practice
Examples from the announcement illustrate the range of the new options.
Fast-changing content
A site can shorten the Edge Cache TTL for content it expects to change quickly, so Cloudflare returns to the origin more often to revalidate and refresh it. The Edge Cache TTL settings are also where TTL can be defined per status code returned by the origin, and where behavior is set for responses that arrive without cache-control instructions.

Slow-changing assets and Cache Reserve
For rarely changing assets such as favicons or logos, a Cache Reserve Eligibility Rule sets exactly which content — and even which asset sizes — are eligible to be written to Cache Reserve, which keeps assets persistently in Cloudflare's cache and cuts egress fees. Previously, enabling Cache Reserve made the entire zone eligible; that remains the recommended approach for those seeking to save origin egress on every resource. The eligibility rule requires a Cache Reserve subscription.

Protecting a slow origin
A surge of traffic against an origin that performs heavy back-end work can produce 524 errors when no origin response arrives before timeout. While origin capacity is being scaled up, a Cache Rule can extend the timeout instead. The historic interval between two successive origin reads was 100 seconds; stretching it lets the site lean more on Cloudflare's cache.

Other rules address different aspects of caching: custom cache keys define how the cache is keyed, strong ETag support influences when cached assets are revalidated, and custom ports let non-standard ports be used for caching decisions. Cache Rules remain accessible from the dashboard, and feature requests go to the Cloudflare Community.



