Vercel stops caching responses with Vary: Cookie: what to check on your site

Vary indicates the elements of a request likely to modify the response. According to Vercel, cookies can multiply variants and produce entries that are rarely reused. The announcement specifies that other supported Vary headers retain their behavior.

Vercel indicates that the affected responses show x-vercel-cache: MISS and the reason vary_key_denied:cookie in the execution logs. These markers help identify the phenomenon. They do not, on their own, measure the perceived time by visitors or the full site load.

Start with an inventory of routes: public content, customer account, dashboard, cart, and pages varying according to a choice. Check the responses produced with and without cookies, then examine the headers and logs. A component or intermediate service can add Vary without the content manager knowing.

Measure important journeys under comparable conditions. The server response, the downloaded resources, and the rendering in the browser all contribute to the experience. If the cache changes, this effect must be isolated from images, JavaScript, or a slow external service.

Vercel's documentation distinguishes two cases: a response truly identical regardless of cookies, and a response that depends on them. This analysis must be carried out route by route. Removing Cookie from Vary without checking personalization can give the cache incorrect information about the content.

For a personalized response, Vercel recommends keeping Cookie in Vary and using Cache-Control: private to avoid storage in a shared CDN cache. The final choice must take into account the entire processing chain, not just a header previewed on a page.

A public catalog may need a different strategy than a client space. A company looking to improve performance must first understand the data and the variations of each path. The edge guide in Canada reminds that geographic proximity is only part of the architecture.

The announced change does not prove that your site is affected. It justifies a targeted check. Keep a measurement baseline before corrections and monitor privacy after any cache modification.

For each concerned route, note the presence of Vary: Cookie, the expected content without login and with two different accounts, the observed cache state, and response time. Compare the same conditions before and after a correction. An identical public page for all and a personalized customer area call for different decisions. This record allows quantifying the problem before touching the cache policy.

Vercel — Vary: Cookie responses no longer cached. Sources consulted on October 1, 2026; the grids and decision examples are an editorial analysis by Daillac.