Proxied responses now cacheable via CDN-Cache-Control headers
By Steven Van ·
Vercel's CDN now caches proxied responses from external backends using CDN-Cache-Control headers, on all plans at no extra cost.
Vercel's CDN can now cache responses proxied to external backends using the CDN-Cache-Control and Vercel-CDN-Cache-Control headers, matching how Vercel already caches responses from its own Functions.
The headers follow the Targeted HTTP Cache Control spec (RFC 9213) and support directives like max-age and stale-while-revalidate, giving fine-grained control over CDN caching without touching browser caching. A backend can return the headers directly, or they can be set in vercel.json under the headers key if the backend can't be modified. The change is live now on all plans at no extra cost, with no configuration changes or redeployments required to take effect.
