This post originated from an RSS feed registered with .NET Buzz
by Scott Watermasysk.
Original Post: More HttpCompression
Feed Title: ScottW's ASP.NET WebLog
Feed URL: /error.aspx?aspxerrorpath=/blog/rss.aspx
Feed Description: ASP.NET and Blogging
I finally got a chance to put Ben'sHttpCompression module up this site. I had to make one
minor tweak to it. During the check for excluded documents, the empty value
returned on the home page for Request.Path* was causing an causing an exception.
After I posted the change it looks like all of the pages are now using
HttpCompression. As mentioned early, while IIS 6.0 compression works well, it is
based on the file extension and not mime type, which causes a lot of misses.
In addition, as was pointed out on the Atom-Syntax
list, there are some clients using Http 1.0 which seem to support
compression. I was under the impression HttpCompression was an Http 1.1 spec
item only, but it appears, I was not completely accurate:
HTTP compression is a long-established Web standard that is only now
receiving the attention it deserves. Its implementation was sketched out in
HTTP/1.0 (
I did a quick check with Fiddler and it looks like this module will also
handle those cases. Please let me know if you see any weirdness with this site.
If all goes well, in a week or two, we will add this module to the asp.net
cluster.
* This site is mapping all requests to the aspnet_isapi, which causes default
documents to no longer work. As a result, Request.Path returns an empty string
instead of /default.aspx for the home page.
Previous Topic
