I had followed the rather simple commands as per the microsoft KB article here:
The server was still not compressing anything and the temporary compression directory remained empty. This was really frustrating, until I ran across this article:
http://panvega.wordpress.com/2008/09/22/http-compression-in-iis/
There is an extra step that technet seems to have forgotten. The above site nails it:
IIS 6′s new security system prohibits ISAPI DLLs from running by default, so you need to tell IIS 6 that it’s okay to let the compression ISAPI DLL run.
- Open the IIS admin tool (inetmgr); drill into your server, and right-click on “Web Service Extensions”
- Choose “Add a new web service extension”. For the extension name, use whatever you want to identify it in the list (I used “HTTP Compression Extension”).
- You need to add a single required file, which is \Windows\System32\inetsrv\gzip.dll, the ISAPI responsible for doing gzip and deflate compression.
- Check the “Set extension status to allowed”, then click OK.
- You should have a new web service extension in your list called “HTTP Compression”, and it should have a status of “Allowed”.