Vercel CDN now respects Cache-Control headers from external origins by default

Vercel's CDN now automatically respects caching headers from external origins by default for new projects. 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. 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; Cache Tags (Vercel-Cache-Tag header) from origins can be used to purge cached content, and existing projects can opt in to the new behavior from the project dashboard. Projects can opt out of caching for specific request paths by setting the x-vercel-enable-rewrite-caching header to 0.

Related

• Vercel CLI commands now scoped to local directory
• Zero-configuration Django support
• Zero-configuration Go backend support
• Anomaly alert configuration now available

Source: tools