What changed
On August 17, 2026, Google Cloud announced support for the targeted CDN-Cache-Control HTTP response header defined by RFC 9213. Origins can now send cache directives specifically for Cloud CDN edge caches without forcing the same directives onto browsers.
Why it matters
Applications often want long shared-cache lifetimes at the CDN while keeping browser caches shorter or more conservative. A standardized targeted header reduces the need for provider-specific cache configuration and makes origin-controlled cache policy more portable across supporting CDNs.
Browser and shared-cache policy can diverge cleanly
With CDN-Cache-Control, an origin can keep ordinary Cache-Control appropriate for user agents while expressing a separate policy for CDN caches. That is useful for frequently redeployed static assets, API responses and pages where edge reuse and client freshness have different requirements.
Header precedence still matters
Google documents precedence among targeted and general cache headers. Builders should test the exact combination they emit rather than assuming CDN-Cache-Control always overrides every other cache rule or product setting.
RFC support improves portability, not uniformity
RFC 9213 standardizes the header shape, but providers can differ in supported directives, defaults and product-specific behavior. Multi-CDN deployments should validate each vendor independently.