3 ms·
Well this is the thing I'm confused about, having worked on some cloudfront stuff last month, documents like https://docs.aws.amazon.com/AmazonCloudFront/latest
by ris 7y ago
Well this is the thing I'm confused about, having worked on some cloudfront stuff last month, documents like https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/header-caching.html https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope... gave me the clear impression that every header cloudfront passes to the origin will be considered a cache key. In particular if you configure it to "forward all headers", which is what would surely be needed to pass this custom "X-Oversized-Header" onwards, it would effectively disable all caching.
I'm clearly going to have to spend another day staring at the cloudfront documentation.
- iliketoworkhard 7y agoAnd why weren’t all headers considered in the cache key to begin with? The key computation will never not be O(1). Only thing I can think of is too many cache entries with the same cache values for the case where requests with different headers produce the same API response. Which could lead to a large cache.