Emit Cloudflare cache tags from the origin before relying on content-group purges

A purge tag works only when cached responses were associated with that tag.

Source facts

Cloudflare documents adding Cache-Tag response headers at the origin so cached content can be invalidated as a group. Several tags can describe one response, allowing a content dependency to span multiple URLs. Cloudflare removes the header before forwarding it to visitors or Workers, so its absence in the visitor response does not show that origin tagging failed.

Source: Cloudflare — Purge cache by cache-tags.

Applicability

This concerns Cloudflare tag-based cache invalidation.

DSE recommendation

DSE recommends designing tags around content dependencies such as a product, section, or shared component rather than opaque deployment accidents. Ensure the origin emits the intended tags on every affected response and keeps their naming stable across releases. Restrict purge credentials and account for the origin traffic needed to refill a large tag group. Keep an untagged control resource in acceptance testing. Ask the content owner to nominate one dependency that spans several URLs, then show where the origin assigns its shared tag. Keep a missing-tag example in the rehearsal to expose incomplete tagging before a release relies on a group purge for correctness.

Verification

Inspect the controlled origin response for the intended tag, populate several related cached URLs, and update their revision markers. Purge the tag and verify all affected resources refresh while the unrelated control remains unchanged. Confirm tagging at the origin instead of expecting the stripped header to appear in a public browser response.

Official reference

Cloudflare — Purge cache by cache-tags. Reviewed October 20, 2026.