Blob Storage Gzip Content-Encoding on WEB requests
With the current set of capabilities, the file blob has a capability of 'ContentEncoding' property. However, it is heavily limited.
It doesn't allow for Blob web-front end to encode files in gzip on-the-fly.
If you set gzip property on the text or html files, which are stored uncompressed, they will fail to download (On Edge and Chrome).
Successful downloads with gzip ContentEncoding only work for gzip-compressed files.
I need Blob storage Web front-end to compress any stored blob on-the-fly whenever browser advertises Compatibility/Acceptability of Encoding type (.e.g. Accept-Encoding:gzip)
just extra clarification
If you'd run Fiddler diagnostics tool and run a download test with the 'Accept-Encoding: gzip' header set,
you'd discover that ContentEncoding property on the blob doesn't implicitly enable the file encoding.
Web response comes in raw un-encoded format, however with the set 'Content-Encoding: gzip' header.
This is where it goes wrong. The web agent can't decode it, since it is not encoded.
In my feature request, I ask to implement Blob Web front-end to do the encoding/compression on the fly.
I don't intend to store a compressed/encoded format of files on the blob storage. I want web service to do it for me when serving requests.