Skip to content
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

Clarify that Pages assets already served from Tiered Cache #18518

Merged
merged 2 commits into from
Jan 7, 2025
Merged

Clarify that Pages assets already served from Tiered Cache #18518

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f1a1dc
Clarify that Pages assets already served from Tiered Cache
irvinebroque Dec 3, 2024
f328dca
Update src/content/docs/pages/configuration/serving-pages.mdx
ToriLindsay Jan 7, 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
2 changes: 1 addition & 1 deletion src/content/docs/pages/configuration/serving-pages.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ In addition, adding caching to your custom domain may cause issues with [Pages r

However, there are some situations where [Cache Rules](/cache/how-to/cache-rules/) on your custom domain does make sense. For example, you may have easily cacheable locations for immutable assets, such as CSS or JS files with content hashes in their file names. Custom caching can help in this case, speeding up the user experience until the file (and associated filename) changes. Just make sure that your caching does not interfere with any redirects or Functions.

Please note that tiered caching is not supported for custom domains on Pages.
Please note that when you use Cloudflare Pages, the static assets that you upload as part of your Pages project are automatically served from [Tiered Cache](/cache/how-to/tiered-cache/) — you do not need to separately enable Tiered Cache for the custom domain that your Pages project runs on.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Please note that when you use Cloudflare Pages, the static assets that you upload as part of your Pages project are automatically served from [Tiered Cache](/cache/how-to/tiered-cache/) — you do not need to separately enable Tiered Cache for the custom domain that your Pages project runs on.
Note that when you use Cloudflare Pages, the static assets that you upload as part of your Pages project are automatically served from [Tiered Cache](/cache/how-to/tiered-cache/). You do not need to separately enable Tiered Cache for the custom domain that your Pages project runs on.


:::note[Purging the cache]

Expand Down
Loading