Skip to content

add bypassTagCacheOnCacheHit option to cloudflare's regional cache documentation #179

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 3 commits into from
Sep 1, 2025
Merged

add bypassTagCacheOnCacheHit option to cloudflare's regional cache documentation #179

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
97789a0
add `bypassTagCacheOnCacheHit` option to cloudflare's regional cache …
dario-piotrowicz Sep 1, 2025
df56d6b
Apply suggestions from code review
dario-piotrowicz Sep 1, 2025
37ab00f
avoid full url
dario-piotrowicz Sep 1, 2025
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
5 changes: 4 additions & 1 deletion pages/cloudflare/caching.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -313,7 +313,10 @@ The regional cache has two modes:
- `short-lived`: Responses are re-used for up to a minute.
- `long-lived`: Fetch responses are re-used until revalidated, and ISR/SSG responses are re-used for up to 30 minutes.

Additionally, lazy updating of the regional cache can be enabled with the `shouldLazilyUpdateOnCacheHit` option. When requesting data from the cache, it sends a background request to the R2 bucket to get the latest entry. This is enabled by default for the `long-lived` mode.
Additionally there are options you can use to customize the behavior of the regional cache:

- `shouldLazilyUpdateOnCacheHit`: Instructs the cache to be lazily updated, meaning that when requesting data from the cache, a background request is sent to the R2 bucket to get the latest entry. This is enabled by default for the `long-lived` mode.
- `bypassTagCacheOnCacheHit`: Instructs the cache not to check the tag cache when there is a regional cache hit. This enables reducing response times. When this option is used you need to make sure that the cache gets correctly purged either by enabling the [automatic cache purge](#automatic-cache-purge) or purging the cache manually. Defaults to `false`.

```ts
// open-next.config.ts
Expand Down