The Artima Developer Community
Sponsored Link

.NET Buzz Forum
IIS 6.0 Compression and Mapping All Requests to ASP.Net

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Scott Watermasysk

Posts: 661
Nickname: scottwater
Registered: Aug, 2003

Scott Watermasysk is an ASP.NET developers. He wrote the .Text blog engine.
IIS 6.0 Compression and Mapping All Requests to ASP.Net Posted: Sep 8, 2004 5:43 AM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Scott Watermasysk.
Original Post: IIS 6.0 Compression and Mapping All Requests to ASP.Net
Feed Title: ScottW's ASP.NET WebLog
Feed URL: /error.aspx?aspxerrorpath=/blog/rss.aspx
Feed Description: ASP.NET and Blogging
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Scott Watermasysk
Latest Posts From ScottW's ASP.NET WebLog

Advertisement

One of things we do weblogs.asp.net to make creating new blogs as simple as possible is map all requests to the aspnet_isapi.dll. This enables the creation of a new blog by adding a single entry in the database. Nothing else needs to happen and the blog is now available on the entire cluster.

Mapping all requests to the aspnet_isapi.dll does come with a couple caveats:

  1. Default Documents no longer work
  2. Static files need to be handled by ASP.Net
  3. We'll save the rest for the next article :)

One of the nice advantages of using IIS 6.0 is the built in HttpCompression actually works[1] . Well, works most of time. It turns out that not only does mapping all requests to the aspnet_isapi cause default documents to stop working, once you get them working (again, we will cover this in the next article), they are no longer compressed. [2][3]

I spent some time tonight with Scott Forsyth attempting to over come this issue. The good news it is possible to HttpCompress "default documents". The bad news is you would need to enable HttpCompression of every single document served by IIS on the server. If it were at least configurable by site, it would probably work.[4]

So we discussed a couple of options/work arounds for this problem. I remember Ben Lowery had written a pretty simple HttpModule for HttpCompression. A quick google search not only brought me to his site, but the first post is about an updated version that fixes a bunch of  bugs (such as the Server.Transfer issue). Sweet!

Hopefully, I will get it posted to this site by the weekend and report back the results a couple of days later.

[1] See Scott Forsyth's excellent articles here and here if you need help setting it up.
[2] Uncompressed
[3] Compressed
[4] See HcScriptFileExtensions

Read: IIS 6.0 Compression and Mapping All Requests to ASP.Net

Topic: [C# Chat] What's on your mind regarding C#? Previous Topic   Next Topic Topic: Plumtree Portal Server and Microsoft Content Management Server Integration Pack

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use