I ran into a problem where my static images, css, js and html content in my local Azure Web Application was not loading.

HTTP Compression: HTTP compression is a capability that is built into web servers and web browsers to make better use of available bandwidth, and provide faster transmission speeds between both. HTTP data is compressed before it is sent from the server: compliant browsers will announce what methods are supported to the server before downloading the correct format; unsupported browsers will download uncompressed data so enabling HTTP compression does not prevent older browsers from viewing the Html content.

Okay, assuming your website is up and you launch your webpage, you're likely to get a server 500 error. If you're running Vista you will be provided with more details of the 500 error, however, if you're running 2008 Server then there is a distinct possibility you will receive no further information. Note: this method will not make use of II7 integration mode, instead it will be running your website under IIS6 compatibility mode for IIS7. Step 1: II7 doesnt support the the traditional web.config file. You have to convert it. Here is how. Open a new console window. c:\windows\system32\inetsrv\appcmd.exe migrate config "website/virtual-directory"

In this article, I will explain how to enable Native Http Compression on your Windows 2003 Server.
We'll cover the basics and provide whats needed for you to setup the compression on your own.

Proposed Index:
 
 IIS6's Compression Background
 Pro's and Con's
 Enabling Native Compression on IIS6
 Testing your compressed pages