INFRA Signal 203
Introducing Cache Response Rules
↗
Engineers who cannot modify origin headers—whether due to team boundaries or inflexible backends—can now strip or rewrite those headers at the CDN layer, directly improving cache hit ratios and reducing origin load. This addresses a class of caching problems that request-time rules could not solve, since the problematic headers only appear after the origin responds.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Cache Response Rules execute after the origin responds but before Cloudflare writes to cache, allowing modification of headers like Set-Cookie, Cache-Control, ETag, and Last-Modified.
The feature requires no origin code changes, letting CDN operators fix caching issues without negotiating changes with backend teams.
Previous Cloudflare cache controls operated at request time, which could not address problems that only manifest in the origin's response headers.
THE CLUSTER