Introducing Cache Response Rules
These are a new rule type that runs after an origin server replies but before Cloudflare caches the content. When and how caching decisions are madeA CDN cache and an origin server work as a pair. Their goal is to answer from the cache whenever possible and only go back to the origin when the edge can’t respond.
- ▪These are a new rule type that runs after an origin server replies but before Cloudflare caches the content.
- ▪When and how caching decisions are madeA CDN cache and an origin server work as a pair.
- ▪Their goal is to answer from the cache whenever possible and only go back to the origin when the edge can’t respond.
Cloudflare Blog files mainly under programming.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The Cloudflare Blog |
| Canonical URL | https://blog.cloudflare.com/introducing-cache-response-rules/ |
| Publication time | Thu, 23 Jul 2026 18:40:38 GMT |
| Retrieval time | 2026-07-26T19:54:40.701Z |
| Last seen | 2026-07-26T19:54:40.701Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | wmEVTKok3HXl |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
BlogApplication ServicesCacheCache Rules+3Show 3 more tags6 TagsShow 6 tagsSelected TagsApplication ServicesCacheCache RulesCDNOptimizationProduct NewsAll tagsMatching tagsNo tags found1.1.1.12FAAbuseAccessAccess Control Lists (ACLs)AccessibilityAccount TakeoverAcquisitionsAddressingAdvanced Certificate ManagerAdvanced DDoSAdvertisingAegisAfricaAfroflareAgent ReadinessAgentsAgents WeekAIAI BotsAI GatewayAI SearchAI-SPMAI WAFAI WeekAlertmanagerAlways OnlineAMDAMPAnalyticsAnonymousAnti MalwareAnycastAPIAPI GatewayAPI SecurityAPI ShieldAPJCAppleApplication SecurityApplication ServicesArea 1 SecurityArgo Smart RoutingASCIIAsiaAthenian ProjectAtlassianAttacksAudit LogsAustinAustraliaAuthenticationAuthyAutomatic HTTPSAutomatic Platform OptimizationAutomationAutoMinifyAuto…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Cloudflare Blog.
Discussion
0 commentsMore from The Cloudflare Blog
