Automatic HTTP compression on Azure blob CDN (gzip)
To increase performance gzip compression on such files is preferred, or even a must have!
This is supported for everyone as of yesterday. See the following blog post for additional info: http://azure.microsoft.com/blog/2015/08/12/new-cdn-features-country-filtering-compression-and-analytics/
Bryan Allott commented
Awesomeness- thank you!
Glenn Drake commented
That's really useful, thanks for listening!
Any update on this guys?? Its been 2 months since you responded.
Reuben Bond commented
Any update on this?
Also interested in an update. Thanks!
Any update on the matter ? gzip is a critical feature!
its now next month - any update on the availability of this?
Mary Smith commented
Is there any update on this issue?
Pedro Sousa commented
Marked as "planned" for almost an year... What about some status update?
Michal Smereczynski commented
Some progress on it?
Ted van der Veen commented
You can store your content GZIPed in Blob storage yourself and serve compressed:
It would be nice though, if Azure can do compression on-the-fly when it comes to serving content in other Storage services like Table Storage!
WHy not also do automatic minification of CSS / JS files???
Sam Blowes commented
Is it possible to acheieve HTTP compression manually?
Stephen Goss commented
This feature is important because loading compressed content to the blob store will not work for those users whose browsers cannot decompress the content. So the blob needs to be served either with gzip (or deflate etc) encoding or without depending on the Accept-Encoding header on the request. This is normally handled by the origin server setting the Vary: Accept-Encoding response header and the CDN serving the appropriate version of the blob to the client.
This conversation is relevant http://social.msdn.microsoft.com/Forums/pl-PL/windowsazuredata/thread/d4641aa0-1444-4d24-a003-b5645e51ffb3
MS say that they will support it.
I would give all my 10 votes for this.