IIS6 Wildcard Mapping to ASP.NET - no file extension results in IIS 404

Posted by Ian Robinson on Server Fault See other posts from Server Fault or by Ian Robinson
Published on 2010-01-14T15:12:59Z Indexed on 2010/04/27 5:34 UTC
Read the original article Hit count: 828

Filed under:
|
|

I'm trying to perform what I understand to be a relatively simple task. I'd like to remove the extensions from the URLs on my website. I have the proper set up in my application to handle and rewrite the URLs - the trouble is I can't get past IIS to actually get to my application without the extensions.

The details:

I'm running IIS6 on Windows Server 2003. I've gone into the web site for my application, gone to the home directory tab, clicked "Configuration" and added a wildcard map to the following file:

c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll

Which I verified is the same as what is used above in the application extensions portion by .ascx, etc.

If I navigate to http://mywebsite.com/Blogs the result is as follows:

HTTP/1.1 404 Not Found
Content-Length: 1635
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 14 Jan 2010 15:04:49 GMT

Which seems to be a standard IIS 404 message. If I navigate to http://mywebsite.com/Blogs.aspx I get my ASP.NET app....

How can I troubleshoot this? I feel like I've double checked everything a dozen times but to no avail. I must be missing something obvious.

Update: Here are the exact instructions given by the asp.net url rewriter that I'm using:

IIS 6.0 - Windows 2003 Server

  • open property page for website / virtual directory.
  • click the 'home directory' tab
  • click the 'configuration' button, select the 'mappings' tab
  • click 'insert' next to the 'Wildcard application maps' section
  • browse to the aspnet_isapi.dll (normally at c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll)
  • Ensure that 'check that file exists' is unchecked
  • Click OK, OK, OK to close and apply changes

Update 2:

I have yet to find a resolution for this. The application does not seem to be receiving the request from IIS, any further ideas?

© Server Fault or respective owner

Related posts about iis6

Related posts about wildcard