Configure Extensionless URL on IIS 6 and IIS 5.x

Description
Table of Contents
Summary

Describes how to use extensionless URLs on IIS 6 and IIs 5.x

Operations
Configure extensionless URLs on IIS 6: Add wildcard to the wildcard application mappings section
How to do it

Refer to article URL Rewriting and scroll down to the Extensionless URLs section in order to redirect all requests to ASP.NET Engine on IIS 6.

By adding a wildcard mapping on the application configuration tab, ASP.NET will handle all incoming requests.

Configure extensionless URLs on IIS 5.x: Add wildcard to the wildcard application mappings section
How to do it

On IIS version 5.x the wildcard mapping can be configured following the steps above:

  1. From the application click Properties and open the virtual folder tab and then click Configuration;
  2. In the executable text box place the path to the “aspnet_isapi.dll“;
  3. In the extension text box specify the “.*” to specify all kinds of extension;
  4. Uncheck option ”Check that file exist
Configure extensionless URLs on IIS 5.x and 6: Handle custom error 404
How to do it

On IIS version 5.x and IS version 6 an alternative method can be used following the steps above:

  1. Configure on the application directory the custom error 404 to the “error404.axd” HTTP handler;
  2. Implement a custom HTTP module that will identify a not handled request and use ASP.NET to open error404.axd?REQUEST-URL.  In the module implementation a URL rewriting will be issued in order to invoke the correct physical page.
Example of how to configure handler for the 404 custom error
(Example of how to configure handler for the 404 custom error)