How To: Enable ASPX Compression in IIS (Part 2)

see Enable ASPX Compression in IIS (Part 1) to start...

In order to edit metabase – go to IIS – computer name >> properties - check - enable direct metabase edit (don't forget to clear it after you finished)

1. open metabase.xml in notepad, make search by word – this section consists of 2 parts: deflate (at the beginning) and GZIP down there (this is what we are looking for) in location section we edit up to the following result:

   Location ="/LM/W3SVC/Filters/Compression/gzip"
                    HcCompressionDll="C:\WINNT\system32\inetsrv\gzip.dll"
                    HcCreateFlags="1"
                    HcDoDynamicCompression="TRUE"
                    HcDoOnDemandCompression="TRUE"
                    HcDoStaticCompression="TRUE"
                    HcDynamicCompressionLevel="10"
                    HcFileExtensions="htm
                            html
                            txt"
                    HcMimeType=""
                    HcOnDemandCompLevel="10"
                    HcPriority="1"
                    HcScriptFileExtensions="asp
                            dll
                            exe
                            aspx">
   

2. Save and clear "direct metabase edit" in IIS.
3. HTTP Compression is now up and running, however Event Log shows warnings for W3SVC-WP processes:
   "The account that the current worker process is running under does not have SeTcbPrivilege, password sync feature and old Digest feature are being disabled."
4. Another time open metabase, do not forget to clear the checkbox (in IIS >> computer name >> properties >> "enable metabase edit"), search for AnonymousPasswordSync, set False to every instance of it you find search for UseDigestSSP - set True to every instance of it you find.
5. Save and clear that damn checkbox :) Running this configuration I have never experienced any problem, except one, that is, when you have routed file download in your app. – for example from one server to another and synchroniously to the client – it may experience reliability problems.

To be continued...

Related Posts:

• How To: Enable ASPX Compression in IIS (Part 1)