Custom HTTP Error Code Handling

[windows_mss]

<customErrors defaultRedirect ="ErrorPage.asp x" mode="On">
<error statusCode="500 " redirect="500.a spx" />
<error statusCode="404 " redirect="404.a spx" />
<error statusCode="403 " redirect="403.a spx" />
</customErrors>

I Used the above code to Handle the HTTP Error Code, My Problem Is as follows,

This My Program URL http://localhost/Work/CustErr/Default.aspx,

When I alter The URL Like This http://localhost/Work/CustErr/Default2.aspx, I Can Able To Get The 404 Error, For Page Not Found,

When I Try This url http://localhost/Senthil/Work/CustErr/Default.asp Or http://localhost/Work/Custrr/Default.aspx both of the url are 404 error,

but my program not caching this one, Default IE Page Cannot Found Page is Displaying In The Browser, how can i over come this problem,

Need Help,

Thanks In Advance

[eagle63]

When I alter The URL Like This http://localhost/Work/CustErr/Default2.aspx, I Can Able To Get The 404 Error, For Page Not Found,

When I Try This url http://localhost/Senthil/Work/CustErr/Default.asp Or http://localhost/Work/Custrr/Default.aspx both of the url are 404 error,

but my program not caching this one, Default IE Page Cannot Found Page is Displaying In The Browser, how can i over come this problem,

The short answer for fixing your problem is that you need to set the custom 404 error page for your website in the IIS configuration. It needs to point to the same location you have configured in the web.config file.

Go in to IIS settings (in MMC). Open the websites folder. Right-click on your website. Choose the Custom Errors tab. Select the 404 Error Message from the list and choose Edit Properties. In the File field enter the local path of your custom ASPX error page.

If you want to understand why, read on.

Your settings in the web.config file only affect files that are mapped to the aspnet_isapi.dl l in IIS. So when you type in a broken URL in your browser that ends with .aspx the IIS server passes that request on to the aspnet_isapi.dl l. It's this .Net handler that determines that the file is missing (404) and then, according to the web.config settings you posted, forwards to the custom error page.

Now lets look at the second broken link you mentioned. The URL has a .asp extension. By default IIS maps .asp files to a different handler (asp.dll). So your broken URL request is passed to the asp.dll to handle the request. The asp.dll finds the same problem (the resource is missing). However, your web.config settings do not affect the asp.dll handler and so your request does not get forwarded to your custom ASP.Net error handler. So, not having any custom settings in place asp.dll passes the 404 error back to IIS. IIS looks at its configuration for custom 404 errors and forwards you to the generic 404 page.

That last broken link has a .aspx extension. So you would think that IIS would handle it with the aspnet_asapi.dl l handler. It should then be forwarding to your configured custom 404 page. However, the catch here is that you have changed the directory name (Custrr) so IIS will first check for the directory to see what the custom Application Mappings are for that directory. Since the directory does not exist IIS goes directly to its own custom 404 page. So it never gets to the aspnet_asapi.dl l.

This isn't an IE problem. However, if your IE is configured to "Show friendly HTTP error messages" it may be adding to the confusion.