Note that there are some explanatory texts on larger screens.

plurals
  1. POAzure CDN - Enabling HTTP Compression - Hosted Web Role
    primarykey
    data
    text
    <p>Has anyone successfully <a href="http://blogs.msdn.com/b/avkashchauhan/archive/2012/03/05/enableing-gzip-compression-with-windows-azure-cdn-through-web-role.aspx" rel="noreferrer">configured Azure CDN for HTTP compression</a> using their hosted web role? We are having trouble compressing HTTP content at the Azure edge servers. The CDN is only caching the uncompressed version of the content. </p> <p>If we hit our resource link (<em>webresource.axd</em>) from a non-Azure approach it compresses via gzip (<em>using the xxxx.cloudapp.net/cdn/webresource.axd</em>) as expected. However, as soon as we point our resource link to Azure CDN (<em>xxxx.vo.msecnd.net</em>), the content is served up uncompressed, despite the browser telling the Azure CDN it accepts gzip.</p> <p>I <a href="http://social.msdn.microsoft.com/Forums/en-US/windowsazuredata/thread/a88c31ff-3890-4b25-a7eb-3ee59f2193d3" rel="noreferrer">posted this same issue to Azure Forums</a>, but nobody has responded as of yet.</p> <p>While troubleshooting the problem, it appears that the Azure CDN is stripping out the <strong>Accept-Encoding</strong> HTTP header. Just curious if others have had this same issue.</p> <p><a href="http://blogs.msdn.com/b/windowsazure/archive/2011/03/18/best-practices-for-the-windows-azure-content-delivery-network.aspx" rel="noreferrer">Azure CDN Best Practices states...</a></p> <blockquote> <p><strong><em>How does the Windows Azure CDN work with compressed content?</em></strong></p> <p><em>The Windows Azure CDN will not modify (or add) compression to your objects. The Windows Azure CDN respects whatever compression is provided by the origin based on the "Accept-Encoding" header. As of 1.4, Azure Storage does not support compression. If you are using hosted-service object delivery, you can configure IIS to return compressed objects.</em></p> </blockquote> <p>What we are seeing is that the CDN is not respecting the origin <strong>Accept-Encoding</strong>, it's being stripped away.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload