This post originated from an RSS feed registered with .NET Buzz by Scott Hanselman. Original Post: HttpCompression = on Feed Title: Scott Hanselman's ComputerZen.com Feed URL: http://radio-weblogs.com/0106747/rss.xml Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios. Latest .NET Buzz Posts Latest .NET Buzz Posts by Scott Hanselman Latest Posts From Scott Hanselman's ComputerZen.com

I noticed that just the HTML on my home page was over 100K, so I turned HttpCompression on with the Blowery HttpCompression Module:

 <configSections> 
  <sectionGroup name="blowery.web">
   <section name="httpCompressionModule" type="blowery.Web.HttpModules.HttpCompressionModuleSectionHandler, HttpCompressionModule"/>
  </sectionGroup>
 </configSections>
 <blowery.web>
  <httpCompressionModule preferredAlgorithm="gzip" compressionLevel="high"/>
 </blowery.web>
<system.web>

However, there's a series of majorly icky bugs in most versions of IE and a few of them are JUST RIDICULOUS. It's bitten me before, so as much as I support companies like XCompress (XCache) and HttpZip and the whole concept of HttpCompression, I'm a little wary.  Let me know if you have a problem.  Of course, if you can't read this, you have a problem. :)