Setting the file. One moment.
Subchapter 7.24
references/support-topics/cdn-cache-auth-safety.mdMarkdown1 KBView on GitHub
Treat edge caching as a safety question first. The route must be a public, cacheable GET path before a shared-cache recommendation is allowed.
Use methodDistribution, cacheBreakdown, and headers. Before s-maxage, rule out cookies, sessions, authorization, draft state, and user-specific data.
Do not cache mutations, dashboards, account data, request-personalized responses, or routes whose value changes per viewer. Do not mix private with shared-cache directives.
Name GET share, cache mix, file line, and policy: mechanism, scope, TTL/freshness, and Vary. If the right policy is no-store, emit no-change/observation.