We are using the Azure CDN with HTTPS and QueryString support.
Using the Azure CDN, we are unable to support HTTP Compression via our hosted web role. We followed
this MSDN Blog example, but it didn't change the compression behavior. For troubleshooting, we logged the IIS request headers that the CDN was relaying and discovered that the CDN Edge Servers (EdgePrism/220.127.116.11) are not passing the
"Accept-Encoding" HTTP header which thus won't allow us to serve up a compressed resource. The MSDN blog also states that the edge servers are using HTTP 1.0, but our IIS logs indicates that it is served up via HTTP 1.1 protocol - telling
us that we don't need the noCompressionForHttp10 and noCompressionForProxies flags anyway.
Why aren't the edge servers relaying the "Accept-Ecoding" HTTP Header? Without this header relay we cannot deliver compressed content via gzip/deflate.
Here are the HTTP Header requests that we've captured from the browser and thru the CDN to our IIS web role.