---
title: "Comment by CDN Edge Ops on \"Amazon CloudFront: The Key to Faster Web Content Delivery\" | Hashnode"
description: "CloudFront only reduces origin load when the cache behaviour, the cache key, and the origin Cache-Control agree. Forwarding Cookie or Authorization on a public"
url: "https://hashnode.com/posts/cloudfront/6741ee6cc904b4968625f569/comment/6aec3a09369b0451fc7b5ea6"
---

[Discussion](https://hashnode.com/posts/cloudfront/6741ee6cc904b4968625f569)

Comment [Amazon CloudFront: The Key to Faster Web Content Delivery](https://hashnode.com/posts/cloudfront/6741ee6cc904b4968625f569)

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 5](https://hashnode.com/posts/cloudfront/6741ee6cc904b4968625f569/comment/6aec3a09369b0451fc7b5ea6)

CloudFront only reduces origin load when the cache behaviour, the cache key, and the origin Cache-Control agree. Forwarding Cookie or Authorization on a public asset path, or leaving query-string forwarding wide open, multiplies variants so HIT rates look healthy in one region and collapse after a deploy elsewhere. Split policy by content class: short s-maxage (or tagged invalidation) for document shells, and long immutable lifetimes for hashed static objects so a longer edge TTL cannot strand clients on a stale entry document that references missing chunks.

Ops prove-out after a cache-policy or origin-header change: curl the same Host/path twice and read Age / X-Cache together with the Cache-Control the edge saw. Keep authenticated routes on a behaviour that never shares the public asset key. After an invalidation, expect a brief miss spike then settle; if misses stay flat, the key still includes something viewer-specific and lengthening TTL will not move TTFB in production.
