From e886c2cf426e750f6af40ddab835501ac7d8fccf Mon Sep 17 00:00:00 2001
From: cf-scott <124814351+cf-scott@users.noreply.github.com>
Date: Mon, 11 Nov 2024 15:01:18 -0800
Subject: [PATCH] Update cache-reserve.mdx

Added O2O caveat, as per cache team review here:
https://chat.google.com/room/AAAAw8D9k0s/m8bhqCpQ10g/m8bhqCpQ10g?cls=10

While Tiered Cache is moving in front of O2O, Cache Reserve is still behind O2O.
---
 src/content/docs/cache/advanced-configuration/cache-reserve.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
index 7673cd8321e1b54..977a10830a6c5b3 100644
--- a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
+++ b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx
@@ -46,6 +46,7 @@ Not all assets are eligible for Cache Reserve. To be admitted into Cache Reserve
 - Be cacheable, according to Cloudflare's standard [cacheability factors](/cache),
 - Have a freshness time-to-live (TTL) of at least 10 hours (set by any means such as Cache-Control / [CDN-Cache-Control](/cache/concepts/cache-control/) origin response headers, [Edge Cache TTL](/cache/how-to/edge-browser-cache-ttl/#edge-cache-ttl), [Cache TTL By Status](/cache/how-to/configure-cache-status-code/), or [Cache Rules](/cache/how-to/cache-rules/)),
 - Have a Content-Length response header.
+- Come from an origin in the eyeball zone, and not from an [O2O](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) origin.
 - When using [Image transformations](/images/manage-images/create-variants/), original files are eligible for Cache Reserve, but resized file variants are not eligible because transformations happen after Cache Reserve in the response flow.
 
 ## Limits