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

New Vercel projects will honor cache-control headers by default when proxying requests to external origins, starting April 6th.

Previously, responses served through rewrites to external origins were uncached by default, and enabling caching required the x-vercel-enable-rewrite-caching header in vercel.json. Now, Vercel's CDN automatically respects your origin's caching headers.

What's changing:

• For new projects, Vercel will cache responses from external origins according to upstream Cache-Control, CDN-Cache-Control and Vercel-CDN-Cache-Control headers by default.

• You can use Cache Tags (Vercel-Cache-Tag header) from your origins to purge cached content.

• Existing projects can opt in to the new caching behavior from the project dashboard.

• You can opt out of caching for specific request paths by setting the x-vercel-enable-rewrite-caching header to 0.

Review your upstream cache headers before April 6th when creating a new project that proxies to external origins without caching, ensuring they reflect your intended caching strategy.

Learn more about Rewrites to External Origins and configure routing in the CDN tab of your project settings.