Scott Hanselman

browse by category or date

HttpCompression = on

January 9, '04 Comments [6] Posted in ASP.NET | HttpModule | Bugs
Sponsored By

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. :)

« Microsoft "MSN Direct" and Wrist.NET app... | Blog Home | Google Juice? Hardly. »

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
Comments [6]
Friday, January 09, 2004 3:45:41 PM UTC
Hey Scott,
Thanks for trying out the compression module. If you have any problems with it, give me a shout.
Ben Lowery
Friday, January 09, 2004 4:15:59 PM UTC
What server are you on? Windows 2000 or 2003? IIS6 on 2003 fixes a lot of the built-in compression issues that plagued IIS5 in 2000. Or are you just wanting to compress your home page?
Darrell
Friday, January 09, 2004 5:10:38 PM UTC
If you use output caching, you should checkout this issue/fix
http://www.pocketsoap.com/weblog/2003/07/1330.html
Simon Fell
Friday, September 03, 2004 6:44:07 PM UTC
IIS6 has fixed the server side bugs. As you mention, there are still bugs in many browsers that cause problems. That is why even when you use IIS6 internal compression you need a tool that will do the browser sensing and serve the correct content for you, avoiding the problem cases. Check out ZipEnable. It adds the preconfigured browser sensing compenent to native IIS6 compression. You can get a free trial at http://www.zipenable.com.
Tad
Saturday, September 04, 2004 7:04:11 PM UTC
Our major problem is that our sites are ENTIRELY under SSL, and most of the browser bugs affect GZIP under SSL. Does ZipEnable grok that?
Scott Hanselman
Saturday, September 04, 2004 7:08:26 PM UTC
Tad, with all due respect, I checked your site, and saw this in the FAQ:

"Modern browsers built after 1996 to the HTTP 1.1 specification can handle compressed content flawlessly (Internet Explorer and Netscape 5 and higher, Mozilla, Opera, etc.)."

That's just not true. Thoughts?
Scott Hanselman
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.