Please note that when you want to do this while at the same time disabling caching, you need to set the maxTtl > 0, otherwise policy validation will fail.
Besides, the design decision to have the "Authorization" header set in the cache policy, while NOT having it in the origin request policy is counter intuitive and hides the fact that this header is actually sent to the origin, since it's not present in the origin request policy. I would propose to require having it in both places instead.
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
- AWS OFFICIALUpdated 6 months ago
- How do I resolve the "No 'Access-Control-Allow-Origin' header is present on the requested resource" error from CloudFront?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago