New Vercel projects will honor by default when proxying requests to external origins, starting April 6th.cache-controlheaders Previously, responses served through rewrites to external origins were uncached by default, and enabling caching required the header in . Now, Vercel's CDN automatically respects your origin's caching headers.x-vercel-enable-rewrite-cachingvercel.json What's changing: 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 and configure routing in the of your project settings.Rewrites to External OriginsCDN tab Read more For new projects, Vercel will cache responses from external origins according to upstream , and headers by default.Cache-ControlCDN-Cache-Control Vercel-CDN-Cache-Control You can use ( header) from your origins to purge cached content.Cache TagsVercel-Cache-Tag 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 header to .x-vercel-enable-rewrite-caching0