HTTP Compression for IIS 6.0

HTTP Compression for IIS 6.0

I just went through and enabled HTTP Compression for the server that ChrisHammond.com, Solo2.org, and various other websites run on. Now, I can't tell if the difference is noticable, or if I just think it's noticable? hmmm

Followed the instructions in this article for setting up HTTP Compression on IIS 6

https://weblogs.asp.net/owscott/archive/2004/01/12/57916.aspx

Recent Comments

Comment Avatar
I've done the same thing on a few servers after reading that same article. And no - you're not imagining things - it makes browsing sites a LOT zippier :) You can verify it by checking complete headers or running an IE plugin that displays everything for each (and cumulative) requests. http://www.iewatch.com (commercial) or http://www.blunck.info/iehttpheaders.html (freeware), etc. I imagine there are similar things for Firefox. There are a couple 'gotchas' still to watch though. If you're hosting software downloads (as in EXE setup files) you'll want to delete those entries from the metabase. I suppose those entries are still in IIS as a throwback to the days when people coded web sites in C or some other compiled language. (There are a few still around that use DLLs and EXEs.) Cheers!
Posted By: Anonymous on Mar 2006

Add Comment

Please add your comment by filling out the field(s) below. Your comment may need to be approved before it becomes visible.
Enter your first name for display with the comment
Enter your last name for display with the comment.
Enter your comment here.
If you can't type DNNRocks in, you can't post, plain and simple.
Submit Comment Cancel

Chris Hammond

Chris Hammond is a father, husband, leader, software developer, photographer and car guy. Chris focuses on the latest in technology including artificial intelligence (AI) and has spent decades becoming an expert in ASP.NET and DotNetNuke (DNN) development. You will find a variety of posts relating to those topics here on the website. For more information check out the about Chris Hammond page.

Find me on Twitter, GitHub and LinkedIn.