You can now see the exact cache key generated for any request directly in Cloudflare Trace. This visibility helps you troubleshoot cache hits and misses, and verify that your Custom Cache Keys — configured via Cache Rules or Page Rules — are working as intended.
Previously, diagnosing caching behavior required inferring the key from configuration settings. Now, you can confirm that your custom logic for headers, query strings, and device types is correctly applied.
Access Trace via the dashboard or API, either manually for ad-hoc debugging or automated as part of your quality-of-service monitoring.
Example scenario
If you have a Cache Rule that segments content based on a specific cookie (for example, user_region), run a Trace with that cookie present to confirm the user_region value appears in the resulting cache key.
The Trace response includes the cache key in the cache object:
{ "step_name": "request", "type": "cache", "matched": true, "public_name": "Cache Parameters", "cache": { "key": { "zone_id": "023e105f4ecef8ad9ca31a8372d0c353", "scheme": "https", "host": "example.com", "uri": "/images/hero.jpg" }, "key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::" }}Get started
To learn more, refer to the Trace documentation and our guide on Custom Cache Keys.
Source: Cloudflare
Latest Posts
- MC1519871: Microsoft Copilot Code Expands to Mobile and Mac with Local Sandbox for Frontier Users

- MC1557760: Microsoft Teams Increases Registration Capacity for Town Halls and Webinars to 20,000

- MC1557764: Agent 365 Business Analytics Adds Access Management for Admin Role and Permission Control

- MC1557754: Microsoft Copilot Adds Usage-Based Billing to Continue Model Access with Copilot Credits







