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?

주제

스토리지 네트워킹 및 콘텐츠 전송

태그

아마존 심플 스토리지 서비스 아마존 CloudFront

언어

English

Jon

질문됨 일 년 전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

관련 콘텐츠