Clarify that Pages assets already served from Tiered Cache #18518
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This line in the docs was confusing and made it sound like you couldn't benefit from Tiered Cache with Pages.
irvinebroque
requested review from
GregBrimble,
WalshyDev,
aninibread,
ToriLindsay and
a team
as code owners
Deploying cloudflare-docs with
|
| Latest commit: |
f328dca
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://811c3c47.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://bib-tc-pages.cloudflare-docs-7ou.pages.dev |
|
Files with changes (up to 15)
|
ToriLindsay
approved these changes
Jan 6, 2025
| @@ -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. | |||
There was a problem hiding this comment.
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This line in the docs was confusing and made it sound like you couldn't benefit from Tiered Cache with Pages.