Expand Azure Front Door Compression Support
Currently AFD only performs compression when CDN caching is enabled and when the cached files are 8MB or less in size.
Please allow for compression to be enabled independently of caching, and allow for files larger than 8MB to be compressed.
Kozak, Daniel commented
Agreed 8MB is definitely a VERY low threshold to have to work with in terms of file size.
James Gilbert commented
We had help with microsoft from this:
there is a setting in IIS which removes the compression when passing through a proxy, When we changed that, it fixed front door removing compression.
Set-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST' -filter "system.webServer/httpCompression" -name "noCompressionForProxies" -value "False"
Restart the W3C service and it should work.
Jeff Brewer commented
Our API does have not have much use for caching given usage patterns and as the data coming back regularly updates.
Our services return compressed data.
Running thru AFD removes the compression.
Please let this just pass thru at the very least.
Seeing about 1mb of data turn into about 8mb is not a good thing.
Anthony Super commented
Having the ability to compress all dynamic content is important for us too - not just static files cached by Front Door.
When serving content directly from our web servers, we can compress all responses - but we lose this when going via Front Door. This adds a huge amount of network overhead for our end users.
Minh Dang commented
I second that request whole-heartedly!!!