Cloudfront invalidation does not clear compressed version of object

I have a cloudfront distribution in front of an S3 bucket to serve a website. A certain S3 object is updated and then an invalidation matching the path is completed.

After that, requests with header 'accept-encoding: gzip, deflate, br' get a stale version of the object, whereas requests without that header get the fresh version. The same edge location is serving the content in both cases.

I assume this has got something to do with cloudfront storing compressed vs uncompressed versions. Why doesn't the invalidation clear the compressed version?

主题

存储网络和内容交付

标签

亚马逊简单存储服务 (S3)Amazon CloudFront

语言

English

Jon

已提问 1 年前223 查看次数

1 回答

最新
投票最多
评论最多

这些答案有用吗？为正确答案投票，以帮助社区从您的知识中受益。

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html indicates "When you invalidate a file, CloudFront invalidates every cached version of the file regardless of the header values", so Cloudfront should have invalidated both.

jhmartin1

已回答 10 个月前

Jon
10 个月前
My observations do not match that documentation. The context in which it is happening for me is reasonably complicated - a Wordpress site which is statically published to S3/Cloudfront. But I might have look to see if I can re-create the problem using simple command line tools.

Cloudfront invalidation does not clear compressed version of object

相关内容