New projects created after March 31st will cache responses from external origins according to upstream Cache-Control / CDN-Cache-Control / Vercel-CDN-Cache-Control headers by default.

Vercel is a platform for deploying modern web applications with speed and simplicity, offering developers a seamless experience for hosting and scaling their projects. With features like instant deployment, serverless functions, and global CDN, Vercel empowers developers to focus on building great user experiences without worrying about infrastructure management.

Vercel

Vercel is changing the default caching behavior for new projects starting April 6th. Previously, responses proxied through rewrites to external origins were uncached by default and required an explicit header to enable caching. Now, Vercel's CDN will automatically honor upstream Cache-Control, CDN-Cache-Control, and Vercel-CDN-Cache-Control headers. Cache Tags can also be used from origins to purge cached content. Existing projects can opt in via the project dashboard, and specific paths can opt out by setting the x-vercel-enable-rewrite-caching header to 0. Developers with new projects proxying to external origins should review their upstream cache headers before April 6th.

Vercel CDN now respects cache-control headers from external origins by default