Purge cache by cache-tags

Cache-tag purging makes multi-file purging easier because you can instantly bulk purge by adding cache-tags to your assets, such as webpages, image files, and more. Note that Tag, Hostname and Prefix purges are only available for Enterprise customers.

General workflow for cache-tags

1. Add tags to the Cache-Tag HTTP response header from your origin web server for your web content, such as pages, static assets, etc.
2. Ensure your web traffic is proxied through Cloudflare.
3. Cloudflare associates the tags in the Cache-Tag HTTP header with the content being cached.
4. Use specific cache-tags to instantly purge your Cloudflare CDN cache of all content containing that cache-tag from your dashboard or using our API.
5. Cloudflare forces a cache MISS on content with the purged cache-tag.

Warning

Be careful when purging. A cache MISS can cause execution delays by requiring a fetch from your origin server.

Add Cache-Tag HTTP response headers

You add cache-tags to your web content in Cache-Tag HTTP response headers to allow the client and server to pass additional information in requests or responses. HTTP headers consist of a specific case-insensitive name followed by a colon : and the valid value, for example, Cache-Tag:tag1,tag2,tag3. Use commas to separate the tags when you want to use multiple cache-tags.

When your content reaches our edge network, Cloudflare:

• Removes the Cache-Tag HTTP header before sending the response to your website visitor or passing the response to a Worker. Your end users or Worker never see Cache-Tag HTTP headers on your Cloudflare-enabled website.
• Removes whitespaces from the header and any before and after cache-tag names: tag1, tag2 and tag1,tag2 are considered the same.
• Removes all repeated and trailing commas before applying cache-tags: tag1,,,tag2 and tag1,tag2 are considered the same.

A few things to remember

• A single HTTP response can have more than one Cache-Tag HTTP header field.
• The minimum length of a cache-tag is one byte.
• Individual tags do not have a maximum length, but the aggregate Cache-Tag HTTP header cannot exceed 16 KB after the header field name, which is approximately 1,000 unique tags. Length includes whitespace and commas but does not include the header field name.
• For cache purges, the maximum length of a cache-tag in an API call is 1,024 characters.
• The Cache-Tag HTTP header must only contain printable ASCII encoded characters.
• Spaces are not allowed in cache-tags.
• Case is not sensitive. For example, Tag1 and tag1 are considered the same.

Purge using cache-tags

1. Log in to your Cloudflare dashboard ↗, and select your account and domain.
2. Select Caching > Configuration.
3. Under Purge Cache, select Custom Purge. The Custom Purge window appears.
4. Under Purge by, select Tag.
5. In the text box, enter your tags to use to purge the cached resources. To purge multiple cache-tagged resources, separate each tag with a comma or have one tag per line.
6. Select Purge.

API

You can purge using cache-tags via the Cloudflare API. For more information, refer to the API documentation. You can purge up to 30 cache-tags per API call and up to 250,000 cache-tags per a 24-hour period.

Resulting cache status

Purging by tag deletes the resource, resulting in the CF-Cache-Status header being set to MISS for subsequent requests.

If tiered cache is used, purging by tag may return EXPIRED, as the lower tier tries to revalidate with the upper tier to reduce load on the latter. Depending on whether the upper tier has the resource or not, and whether the end user is reaching the lower tier or the upper tier, EXPIRED or MISS are returned.

Was this helpful?

What did you like?

Accurate

Easy to understand

Solved my problem

Helped me decide to use the product

Other

What went wrong?

Hard to understand

Incorrect information

Missing the information

Other

Thank you for helping improve Cloudflare's documentation!