Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I remember attempting to use an extension-less URL format in a CMS I wrote way back when .NET 2.0 first came out. The problem was deploying to an IIS6 server. It made it practically impossible. I had to programmatically create folders for the path (tons of folders) and insert a dummy "Default.aspx" in there to get the request routed to ASP.NET. Of course, I hated that "solution" and had to abandon using extension-less URLs.

Now that I am getting started with ASP.NET MVC, I again want (need) to use extension-less URLs. Can somebody tell me if I am going to have the same headaches when I try to deploy my app to IIS6? Is anything special required to get this type of URL structure to work in IIS6?

share|improve this question

Extension-less URLs are possible with IIS 6, but it requires setting up a "wildcard" ISAPI mapping in the site's Application Config. This has the downside of causing all requests to get processed by the ASP.NET ISAPI filter including static files like images, javascript, etc.

Here is an excellent blog post from Phil Haack about the different options for setting up ASP.NET MVC on IIS 6. The wildcard instructions are about halfway down.

share|improve this answer
Yeah there are definitely performance implications with passing all requests to aspnet_isapi.dll. Crap. If Windows Server 2008 was not so damn expensive, I would upgrade! – Josh Stodola Jan 7 '10 at 16:28
Looking at the comments, it appears like there are other issues that spring up as well. And most of them Dr. Phil does not even respond to! – Josh Stodola Jan 7 '10 at 16:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.