From d82631a8c2ac4f8b8f8319fe8a56c9a048c4e49a Mon Sep 17 00:00:00 2001 From: nenizera Date: Thu, 29 May 2025 16:27:06 +0100 Subject: [PATCH] [cache] Update purge-by-tags.mdx Per product's name, Tiered Cache. --- src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx index 594bb1849c6124..ac23b85ba1aec4 100644 --- a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx +++ b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx @@ -60,5 +60,5 @@ For information on rate limits, refer to the [Availability and limits](/cache/ho Purging by tag deletes the resource, resulting in the `CF-Cache-Status` header being set to [`MISS`](/cache/concepts/cache-responses/#miss) for subsequent requests. -If [tiered cache](/cache/how-to/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. +If [Tiered Cache](/cache/how-to/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.