Skip to content

Update workers-cache-rules.mdx #26832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 2, 2025
+7 −7
Merged

Update workers-cache-rules.mdx #26832

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions src/content/docs/cache/interaction-cloudflare-products/workers-cache-rules.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,26 +9,26 @@ head:

---

Your Workers script can override [cache rule](/cache/how-to/cache-rules/) behavior, whether it is applied to a zone using Cloudflare or a zone that is not proxied through Cloudflare.
Your Workers script can override [Cache Rules](/cache/how-to/cache-rules/) behavior, whether it is applied to a zone using Cloudflare or a zone that is not proxied through Cloudflare.

For example, if there is a cache rule configured to bypass cache for `example.com/foo`, but your Workers script sets `cacheEverything: true`, the script's setting will take precedence, and the request will be cached. The same applies if the request is made to a non-Cloudflare zone — the Worker's `cacheEverything` setting will still override.

## Precedence order

Cache behavior is determined by the following order of precedence:

1. Workers script settings
2. Cache rules
3. Page rules
1. [Workers](/workers/) script settings
2. [Cache rules](/cache/how-to/cache-rules/)
3. [Page rules](/rules/page-rules/)

Cache rules override page rule settings, and Workers scripts override cache rules. Among rules at the same level, the one with the highest specificity takes priority.

## Compatibility flags

This override behavior is controlled by [compatibility flags](/workers/configuration/compatibility-flags/):

- For the Fetch API: `request_cf_overrides_cache_rules`
- For the Cache API: `cache_api_request_cf_overrides_cache_rules`
- For the [Fetch API](/workers/runtime-apis/fetch/): `request_cf_overrides_cache_rules`
- For the [Cache API](/workers/runtime-apis/cache/): `cache_api_request_cf_overrides_cache_rules`

These flags must be enabled to allow Workers scripts to override cache rules.

Expand All @@ -50,4 +50,4 @@ If your Worker has an earlier compatibility date than the ones listed above, the

If a cache rule is configured to bypass cache for `example.com/foo`, and a Worker with a compatibility date of `2025-04-02` or earlier tries to set `cacheEverything: true`, the cache rule will take effect, and the response will not be cached.

Likewise, if using the Cache API without `cache_api_compat_flags` enabled, even if you enable `cache_api_request_cf_overrides_cache_rules`, the Cache API will not take effect.
Likewise, if using the Cache API without `cache_api_compat_flags` enabled, even if you enable `cache_api_request_cf_overrides_cache_rules`, the Cache API will not take effect.
Loading