Summary
On July 23, 2026, Cloudflare launched Cache Response Rules, which let customers modify cache behavior based on the origin's response - adjusting headers like Set-Cookie and Cache-Control at the right processing stage so responses that previously blocked caching can now be cached.
What changed
Cache Response Rules add a response-phase control point where Cloudflare can rewrite or strip caching-relevant headers (such as Set-Cookie and Cache-Control) after the origin replies, letting operators make otherwise-uncacheable responses cacheable without changing origin code.
Why it matters
Headers like Set-Cookie routinely prevent caching and quietly erode hit rates; moving the fix to Cloudflare's edge as a rule means teams can reclaim cacheability without touching origin applications. It gives platform teams finer, declarative control over cache behavior and can cut origin load and latency.
Evidence excerpt
Cache Response Rules allows manipulation of cache behavior by adjusting headers like Set-Cookie and Cache-Control at the appropriate processing stage, addressing issues that previously prevented proper caching.