docs: Add Cloud CDN and caching concept page#694
Open
developerjamiu wants to merge 2 commits into
Open
Conversation
developerjamiu
force-pushed
the
cloud-cdn-page
branch
from
July 20, 2026 10:19
fff4bb6 to
951f5da
Compare
developerjamiu
force-pushed
the
cloud-cdn-page
branch
from
July 21, 2026 12:05
a5b5d9e to
92ff573
Compare
This file contains hidden or 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
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.
Adds a new Cloud concept page, Content delivery and caching (
cloud_docs/concepts/cdn.md), documenting the recently launched CDN feature.The page covers:
Cache-Controlpatterns do at each.cacheControlFactory, with the recommendedpublic, max-age=60, s-maxage=86400header.ageresponse header (GET, not HEAD).Technical claims were checked against the framework source at current main, the cloud repo (E2E deploy test, CLI command surface), and a live cache-opted-in deployment. A few platform facts would benefit from cloud-team confirmation on review:
Planned follow-ups in separate PRs: correct the default-caching claims on the framework Flutter web page (they predate the current uniform
no-cache, privatedefault), and add a one-line note to the Deployments page that a successful deploy clears the CDN cache.