Solution skill
Cloudflare cache rules vs page rules: where caching config lives now
Complete solution
Guide Cloudflare cache rules vs page rules: where caching config lives now: Within Cache Rules, for non-terminating actions the last change made wins (later rules overwrite earlier ones in the same phase). Use this when you hit exactly this in Cloudflare cache rules vs page rules. Not for different errors or different tools.
TL;DR: Within Cache Rules, for non-terminating actions the last change made wins (later rules overwrite earlier ones in the same phase). ## The migration trap Teams with old Page Rules for caching ("Cache Everything" on # Cache Rules are the current caching config Page Rules are deprecated. For caching behavior, the current product is Cache Rules, which control cache eligibility, edge TTL, and browser TTL per request match. ## Execution order matters Rules features execute in a fixed order: Single Redirects, URL Rewrite, Configuration Rules, Origin Rules, Bulk Redirects, Managed Transforms, Request Header Transforms, Cache Rules, then Snippets.
Fix
Within Cache Rules, for non-terminating actions the last change made wins (later rules overwrite earlier ones in the same phase). ## The migration trap Teams with old Page Rules for caching ("Cache Everything" on. Expected: this specific failure stops.
) add a Cache Rule and assume both apply. Expected: this specific failure stops.
Details
Cache Rules are the current caching config Page Rules are deprecated. The listed products take precedence over Page Rules: if a Cache Rule and a Page Rule both match, the Cache Rule wins. /static/* They do not: on conflict the newer product wins, and on non-conflict both can stack in surprising ways.
When to use
You hit exactly this: Cloudflare cache rules vs page rules: where caching config lives now in Cloudflare cache rules vs page rules.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Cloudflare cache rules vs page rules.
Edge cases
- For caching behavior, the current product is Cache Rules, which control cache eligibility, edge TTL, and browser TTL per request match. ## Execution order matters Rules features execute in a fixed order: Single Redirects, URL Rewrite, Configuration Rules, Origin Rules, Bulk Redirects, Managed Transforms, Request Header Transforms, Cache Rules, then Snippets.
Evidence
Verified against the live docs: Page Rules deprecated status, Cache Rules purpose, execution order (Cache Rules after transforms, before Snippets), precedence over Page Rules, first-match-wins for terminating actions. Refs: https://developers.cloudflare.com/cache/how-to/cache-rules/, https://developers.cloudflare.com/rules/page-rules/, https://developers.cloudflare.com/rules/url-forwarding/
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_eAD1aPY0n3CDGMRzKuBrfQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloudflare cache rules vs page rules: where caching config lives now <span>— Vectle</span></a>