Vercel’s CDN, which can proxy requests to external backends, now caches proxied responses using the
This is available starting today, on all plans, at no additional cost.
Per the Targeted HTTP Cache Control spec (RFC 9213), these headers support standard directives like
You can return the headers directly from your backend, or define them in
No configuration changes or redeployments required. Return the header (or set it in
Learn more about CDN-Cache-Control headers.
Read more
Continue reading...
CDN-Cache-Control and Vercel-CDN-Cache-Control headers. This aligns caching behavior for external backends with how Vercel Functions are already cached.This is available starting today, on all plans, at no additional cost.
Per the Targeted HTTP Cache Control spec (RFC 9213), these headers support standard directives like
max-age and stale-while-revalidate, enabling fine-grained control over CDN caching without affecting browser caches.You can return the headers directly from your backend, or define them in
vercel.json under the headers key if your backend can't be modified.No configuration changes or redeployments required. Return the header (or set it in
vercel.json) to improve performance, reduce origin load, and ensure fresh content.Learn more about CDN-Cache-Control headers.
Read more
Continue reading...