Cloudflare Launches Cache Response Rules to Fix Origin Caching Issues
Cloudflare Blog · rss · 2026-07-24
Cloudflare announced Cache Response Rules, a new feature allowing modifications to response headers after the origin server replies but before the content is written to the CDN cache.
Core Problem Solved
Origin servers often return headers like Set-Cookie or incorrect Cache-Control directives that inadvertently make cacheable assets uncacheable. This leads to poor cache hit ratios, wasted origin bandwidth, and degraded performance. Previously, fixing this required changing origin code, writing complex Worker scripts, or accepting the performance hit.
How It Works
- Request Phase (Cache Rules): Determines whether to cache, identifies the cache key, and sets edge TTL.
- Response Phase (Cache Response Rules): Intercepts after the origin replies. It can strip cache-busting headers (like Set-Cookie, ETag), rewrite Cache-Control directives, or set cache tags. In conflicts, response rules override request rules.
Currently, the feature supports three primary actions: stripping problematic headers, rewriting origin cache directives, and setting cache tags.
More from Infra
- Leaked DeepSeek transcript says the company has only 20,000 H-equivalent cards — fiiiiiist · 2026-07-24
- Investor Critique: Etching Transformers Into Silicon Is Inherently Limiting — JosephJacks_ · 2026-07-24
- Huawei’s 4:1 GB300 claim shrinks to 2:1 on memory bandwidth, thread says — zephyr_z9 · 2026-07-24
- NVIDIA introduces NVFP4 for faster LLM inference with less GPU memory — NVIDIA Developer · 2026-07-24
- DeepSeek-V4-Flash reaches 105 tok/s on two 4090D cards after Triton kernel rewrites — iSevenDays · 2026-07-24
- Analyst: We Are Still in the First Generation of Rack-Scale AI Compute — BenBajarin · 2026-07-24