You have to map the specific file extensions through the asp.net ISAPI filter. It worked on your workstation because the development web server routes all request through ASP.NET. But in IIS you have to map each specific extension type through the processing filter you want, so you could pass .php to the PHP filter and .aspx through ASP.NET filter. I hope this makes sense to you, there are many examples online on how to map the file extensions in IIS. If you are on a shared hoster or in a shared corporate environmwent where you do not have root access you will have to get them to do this for you (good luck!!).

Thank you, but I did that and still I'm not getting my 404 custom page for any extension different from .aspx I dont know what else to do.

maricusa:

Thank you, but I did that and still I'm not getting my 404 custom page for any extension different from .aspx I dont know what else to do.

 

Hi maricusa,

The resouces with .html, .ccc, and .whatever extension by default not handled by ASP.NET, because the requests for these resources will not be routed to ASP.NET ISAPI. However, the “customErrors” feature is provided by ASP.NET runtime. Since ASP.NET don’t handle these requests, the customErrors feature doesn’t work is the expected behavior.

As docluv said, you should add IIS mapping for these file extensions to ASP.NET ISAPI. I know you did that from your post but I would like to know how you did that exactly. For your reference, I provide the following steps below. Hope they are helpful to you. 

    1. Open IIS manager.
    2. Right click the virtual directory of your web application, and then select “Properties”.
    3. In the “Directory” tab, click the “Configuration…” button.
    4. Click the “Add…” buttion to add mapping. For example, Exectable: C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll        Extension: .ccc

However, this method only works for the mapped resources. If you want to provide the 404 error custom page for all the resouces with whatever extension, you should define “Custom Errors” in IIS. For example, please refer to the following steps:

    1. Open IIS manager.
    2. Right click the virtual direcory of your web application, and then select “Properties”.
    3. Click the “Custom Errors” tab.
    4. Double click the “404” item, which default content is “C:\WINDOWS\help\iisHelp\common\404b.htm”.
    5. Change the “Message type” to “URL”.
    6. Set the url of your custom page. For example: /VirtualDirectoryName/PageName.html

 

ASP and PHP extensions are not processed by the ASP.NET DLL, so your ASP.NET redirect in your web.config cannot act on them.  A custom error page defined in IIS is the proper way to handle this, not mapping extensions.  See www.iis.net for help on IIS, same login as here.

Jeff

Thank you very much. Finally it worked but now I am seeing something weird. I'm working with aspxerrorpath to capture the page the user is trying to reach. this works fine when is .aspx page, I mean when I type testpage.aspx and that page doesnt exist I get the correct asperrorpath, but when I type testpage.html Im redirected to my custom error page but what I get in asperrorpath is the path of my custom error page. Is this the correct behaviour for a custom error page with pages different that .aspx or there is something obviously wrong?

maricusa:

but when I type testpage.html Im redirected to my custom error page but what I get in asperrorpath is the path of my custom error page. Is this the correct behaviour for a custom error page with pages different that .aspx or there is something obviously wrong?

 

Hi maricusa,

The “aspxerrorpath” querystirng paremeter is appended by ASP.NET. IIS doesn’t do that job. This is by design.

If you want the “aspxerrorpath” querystirng paremeter for .htm resource, add .htm extension mapping in IIS. I have already listed the steps in my previous post. Just one thing to append: uncheck the “Check that file exists” option in the “Add/Edit Application Extension Mapping” dialog when add extension mapping.