Vercel CDN now respects Cache-Control headers from external origins by default
By Steven Van ·
The default takes effect for new projects on April 6; existing projects can opt in from the dashboard or disable caching per path with a header.
New Vercel projects will cache responses from external origins by default starting April 6, honoring the origin's Cache-Control, CDN-Cache-Control and Vercel-CDN-Cache-Control headers when proxying through rewrites. Previously, these responses were uncached by default, and caching required adding the x-vercel-enable-rewrite-caching header to vercel.json.
- Existing projects can opt in to the new caching behavior from the project dashboard.
- Caching can be turned off for specific paths by setting x-vercel-enable-rewrite-caching to 0.
- A Vercel-Cache-Tag header from the origin can be used to purge cached content by tag.
Anyone creating a new project that proxies to an external origin should review their upstream cache headers before April 6 to make sure they reflect the intended caching strategy.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →