Why give a cached gzip object?

Question

Hi  
  
I've added support for brotli enabled servers and already gzip too before times.  
and then was push to invalidation ALL contents.  
  
First case, contents fetch with "Accept-Encoding: br, gzip" first then got a response content encoded by "br", and then if I fetch with just gzip I get gzip OK.  
  
Second case, after invalidation, contents fetch first with gzip then got a response gzip content, then request with "Accept-Encoding: br, gzip", Edge has been responding with cached "gzip" content.

Please investigate to this.  
  
Edited by: hedy on Oct 6, 2020 4:09 PM

Answer

well.. I've made sense throught that has been explained "When caching compressed objects is enabled for both compression formats" session in this document to behavior about enabled both type compression.   
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/controlling-the-cache-key.html#cache-key-understand-cache-policy-settings  
  
It hope you help

Answer

in myself, understood this behavior through docs.

Answer

I also saw this. gzip seems to take precedence in the edge cache. I think it's a bug, and I mentioned it on another thread, but there was no reply. I think this makes Brotli support useless currently.

Answer

Thanks, yes I agree it makes sense to serve gzip out of the cache rather than to fetch brotli from the origin, which would take probably take longer at all. I think it should still prioritise br if it has both in the cache and I'm not sure it does but that is not so important.

Why give a cached gzip object?

関連するコンテンツ