Issue with Missing x-cache Header on Certain CDNs in AEM as a Cloud Service I'm working on an AEM as a Cloud Service project where I have cache-control rules set in the response headers.I receive the following headers in my response:accept-ranges: bytesage: 76cache-control: max-age=1800, stale-while-revalidate=1800, stale-if-error=1800, public, immutablecontent-encoding: gzipcontent-length: 27820content-type: text/css;charset=utf-8date: Thu, 06 Feb 2025 13:47:49 GMTlast-modified: Thu, 06 Feb 2025 13:46:28 GMTstrict-transport-security: max-age=31500vary: Accept-Encodingx-cache: HITx-content-type-options: nosniffx-frame-options: Originx-served-by: cache-BOMx-timer: VE13x-vhost: my projectHowever, I'm noticing inconsistent behavior with the x-cache header. In some cases, when served by certain CDNs (e.g., x-served-by: cache-BOM), I see x-cache: HIT or x-cache: MISS, indicating whether the request was served from cache.But with other CDNs (e.g., x-served-by: cache-Hyd), the x-cache header is completely missing from the response, even though the response clearly in