Configuring Proxy Edge Cache Rules FAQ
Running a community platform requires balancing fast delivery for static assets with precise routing for personalized member data. Edge caching provides a way to serve assets from proxy locations while protecting dynamic pages. Below is an administrative FAQ on configuring edge rules, handling custom cache keys, navigating plan limits, and clearing assets efficiently.
What are edge Cache Rules and how do they function?
Edge Cache Rules allow administrators to customize how a proxy edge handles caching for incoming traffic. As detailed in the Cache Rules · Cloudflare Cache (CDN) docs, these rules let you adjust which matching requests are eligible to cache, where that content should be stored, and how long it should remain cached. They can also trigger specific interactions between caching layers and other Rules products for matching requests.
By evaluating incoming requests, an administrator can establish parameters that keep static community media stored at edge locations while ensuring dynamic requests—such as personalized user accounts and changing member views—are not improperly retained. For administrators navigating proxy setups, understanding avoiding edge caching pitfalls on Cloudflare CDN is vital before introducing custom rules.
How many Cache Rules can administrators configure across different plans?
The total number of available Cache Rules depends directly on the tier of service you use. The rule allowances per plan are structured as follows:
- Free plan: 10 rules
- Pro plan: 25 rules
- Business plan: 50 rules
- Enterprise plan: 300 rules
All of these service tiers support Cache Rules. Community managers operating on the Free tier can build up to 10 distinct rules, which is typically sufficient to isolate static assets from sensitive community routes, whereas larger organizations on Enterprise plans have access to 300 rules.
How do you create and manage these edge rules?
Administrators have multiple options for creating and maintaining rules. You can build rules directly in the web dashboard, submit them through the API, or configure them programmatically using Terraform. To assist with setup, ready-made rules templates exist for common use cases.
To inspect and deploy these templates, go to the Rules Overview page within your dashboard and choose the Templates option. You can also explore the developer documentation examples gallery to find inspiration for common routing patterns. Reviewing guides on Cloudflare cache rules for forum avatars and emotes can also clarify how to structure your rule criteria.
How do custom cache keys affect single-file purges?
When a rule defines a custom cache key, the resulting cached resource is indexed by that specific key rather than by the request URL alone. How that custom key is structured directly dictates whether a dashboard single-file purge will succeed.
If a custom cache key alters only the handling of query strings—such as ignoring the query string entirely—a dashboard single-file purge will generally function as expected. However, if your custom cache key includes headers, cookies, or other request properties, single-file purging from the dashboard is prevented because the web dashboard interface cannot submit those custom values in its purge request. In addition, even in the absence of custom Cache Rules, default edge cache keys incorporate specific request headers, which can sometimes stop dashboard single-file purge operations from succeeding on those cached resources.
What options exist when dashboard single-file purge cannot be used?
When custom cache keys or header dependencies block the dashboard single-file purge mechanism, administrators have alternative methods available to clear cached assets:
- API purge by URL: You can send an API request to purge by URL, provided you include all cookies, headers, and query strings configured in your custom cache key. If any cookie or header is omitted from the API purge call, it is evaluated as an empty value in the cache key.
- Purge by host: This clears every cached asset associated with a specific hostname and is unaffected by custom cache key configurations.
- Purge by prefix: This removes all cached content located beneath a specified URL path without being disrupted by custom cache keys.
- Purge by tag: This method clears resources labeled with specific tags and is not affected by custom cache keys.
- Purge everything: This clears all cached assets across the entire zone.
How can you verify that a rule is triggering for matching URLs?
Troubleshooting edge caching behavior is necessary to ensure dynamic profiles are properly routed while media assets cache reliably. According to the Cache Rules · Cloudflare Cache (CDN) docs, you can use Cloudflare Trace to evaluate your setup. Running a trace helps determine whether an active rule is triggering for any specific URL, enabling administrators to verify their matching criteria before unexpected caching occurs.
Sources
Published October 29, 2026. No affiliate links on this page. Facts come from the sources linked above; check them for updates.