Include custom-key request properties in Cloudflare single-file purge planning

A dashboard URL purge cannot always identify a header- or cookie-specific cached object.

Source facts

Cloudflare documents that single-file dashboard purges generally cannot clear custom keys containing headers, cookies, or other unavailable request properties. The API can include the relevant values; missing values are treated as empty in the key. A purge of a cached redirect removes that redirect, not the content stored at its destination URL.

Source: Cloudflare — Purge by single-file.

Applicability

This concerns Cloudflare single-file invalidation.

DSE recommendation

DSE recommends documenting invalidation when designing the cache key, rather than after stale content appears. Record the exact final resource URL and required key dimensions. Use a broader supported prefix or tag purge when individual variants cannot be enumerated safely. Keep API credentials narrowly scoped and outside tickets or browser screenshots. Avoid repeatedly purging a redirecting alias when the stale resource actually lives at its destination. Have the release owner enumerate the supported variants before selecting URL purge as the deployment method. Include one nondefault key value in the rehearsal and keep the resolved redirect destination beside the public alias. Treat an unenumerated variant as an invalidation gap requiring a different method.

Verification

Create controlled cached variants with visible revision markers, update the origin, and perform the intended targeted purge. Request each variant again and compare its content and status. Follow any redirect chain and verify the destination independently so success is tied to the cached object that needed refreshing.

Official reference

Cloudflare — Purge by single-file. Reviewed October 20, 2026.