From 11b5779853e1f664e70073eeb83d00845a2676d1 Mon Sep 17 00:00:00 2001 From: jgomes-cloudflare Date: Thu, 5 Dec 2024 14:13:41 +0000 Subject: [PATCH 1/2] [Cache] Update configure-cache-status-code.mdx --- src/content/docs/cache/how-to/configure-cache-status-code.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cache/how-to/configure-cache-status-code.mdx b/src/content/docs/cache/how-to/configure-cache-status-code.mdx index c80fde5a5349bf1..ff6b5c4d038af13 100644 --- a/src/content/docs/cache/how-to/configure-cache-status-code.mdx +++ b/src/content/docs/cache/how-to/configure-cache-status-code.mdx @@ -4,7 +4,7 @@ pcx_content_type: how-to --- -Enterprise customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource’s origin. +Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource’s origin. Setting cache TTL based on response status overrides the [default cache behavior (standard caching)](/cache/concepts/default-cache-behavior/) for static files and overrides cache instructions sent by the origin web server. To cache non-static assets, set a [Cache Level of Cache Everything using a Cache Rule](/cache/how-to/cache-rules/create-api/#example-requests). Setting `no-store` **Cache-Control** or a low TTL (using `max-age`/`s-maxage`) increases requests to origin web servers and decreases performance. From 2455f1af0eac2a3d170f82e97a732bbe4c292f2a Mon Sep 17 00:00:00 2001 From: Nic <123965403+ngayerie@users.noreply.github.com> Date: Thu, 5 Dec 2024 15:28:42 +0100 Subject: [PATCH 2/2] Update src/content/docs/cache/how-to/configure-cache-status-code.mdx Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> --- src/content/docs/cache/how-to/configure-cache-status-code.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cache/how-to/configure-cache-status-code.mdx b/src/content/docs/cache/how-to/configure-cache-status-code.mdx index ff6b5c4d038af13..190551d6350d5de 100644 --- a/src/content/docs/cache/how-to/configure-cache-status-code.mdx +++ b/src/content/docs/cache/how-to/configure-cache-status-code.mdx @@ -4,7 +4,7 @@ pcx_content_type: how-to --- -Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource’s origin. +Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource's origin. Setting cache TTL based on response status overrides the [default cache behavior (standard caching)](/cache/concepts/default-cache-behavior/) for static files and overrides cache instructions sent by the origin web server. To cache non-static assets, set a [Cache Level of Cache Everything using a Cache Rule](/cache/how-to/cache-rules/create-api/#example-requests). Setting `no-store` **Cache-Control** or a low TTL (using `max-age`/`s-maxage`) increases requests to origin web servers and decreases performance.