From 6dcea968d1ac3ab47821089bfb38fba02571e529 Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Tue, 24 Jun 2025 17:53:45 +0100 Subject: [PATCH 1/2] Adds clarification about `Cloudflare-Cdn-Cache-Control`. --- src/content/docs/cache/concepts/cache-control.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/cache/concepts/cache-control.mdx b/src/content/docs/cache/concepts/cache-control.mdx index 3668c8ec7e2f1f4..7c30e14761db688 100644 --- a/src/content/docs/cache/concepts/cache-control.mdx +++ b/src/content/docs/cache/concepts/cache-control.mdx @@ -196,6 +196,10 @@ Certain scenarios also affect Origin Cache Control behavior when it is enabled o +:::note +When the `Cloudflare-Cdn-Cache-Control` header is set, OCC is effectively turned **on** (regardless of whether OCC is enabled or disabled). As a result, we apply our Authorization header logic (per [RFC 7234, Section 3.2](https://tools.ietf.org/html/rfc7234#section-3.2)) to allow only the `s-maxage`, `must-revalidate`, or `public` directives. If any other directive is present, we do not cache the asset and instead return `BYPASS`. +::: + ## Examples Review the examples below to learn which directives to use with the `Cache-Control` header to control specific caching behavior. From 33bd9b525616a35af8cd1baf3edc30f6eb306ef2 Mon Sep 17 00:00:00 2001 From: angelampcosta <92738954+angelampcosta@users.noreply.github.com> Date: Wed, 25 Jun 2025 17:02:35 +0100 Subject: [PATCH 2/2] Update src/content/docs/cache/concepts/cache-control.mdx --- src/content/docs/cache/concepts/cache-control.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cache/concepts/cache-control.mdx b/src/content/docs/cache/concepts/cache-control.mdx index 7c30e14761db688..e305f3ede0f8f21 100644 --- a/src/content/docs/cache/concepts/cache-control.mdx +++ b/src/content/docs/cache/concepts/cache-control.mdx @@ -197,7 +197,7 @@ Certain scenarios also affect Origin Cache Control behavior when it is enabled o :::note -When the `Cloudflare-Cdn-Cache-Control` header is set, OCC is effectively turned **on** (regardless of whether OCC is enabled or disabled). As a result, we apply our Authorization header logic (per [RFC 7234, Section 3.2](https://tools.ietf.org/html/rfc7234#section-3.2)) to allow only the `s-maxage`, `must-revalidate`, or `public` directives. If any other directive is present, we do not cache the asset and instead return `BYPASS`. +When the `Cloudflare-Cdn-Cache-Control` header is set, OCC is turned **on** (regardless of whether OCC is enabled or disabled). As a result, we apply our Authorization header logic (per [RFC 7234, Section 3.2](https://tools.ietf.org/html/rfc7234#section-3.2)) to allow only the `s-maxage`, `must-revalidate`, or `public` directives. If any other directive is present, we do not cache the asset and instead return `BYPASS`. ::: ## Examples