Home/ Questions/Q 6543937
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T11:24:22+00:00

I’m having a problem with my site: Custom errors aren’t working for me. This

  • 0

I’m having a problem with my site:

Custom errors aren’t working for me. This should redirect general errors to a page, and 404 errors to another. It works locally but not in the hosted environment.

<customErrors defaultRedirect="GeneralError.aspx" mode="on">
    <error statusCode="404" redirect="404Error.aspx" />
</customErrors>

Edit: Ok i tested the error thing a little more, and it seems to work for pages like:

http://www.[domain].com/doesntexist.aspx

but not for

http://www.[domain].com/doesntexist

It only works if i put .aspx there.

Edit: anyone knows how i can make it so it works for both instances?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This has to do with your configuration and version of IIS your host is running. In versions of IIS before 7, or if you are running IIS 7 with the “classic pipeline”, there are actually two channels that http requests go though. One handles .net requests though ASP.net, and the other pipeline goes to IIS. (i.e. ASPX goes to asp.net and .jpg goes to IIS)

    In your case, non existent pages are going to IIS, this your asp.net congi you specified does not apply. I bet if you type in http://www.[domain].com/doesntexist.jpg it will not go to you custom page but if you type http://www.[domain].com/doesntexist.aspx it will.

    Sp there are several solutions based on what version if IIS you have. If your host is using IIS7, then you can run the site with the Integrated Pipeline, meaning all request go through ASP.net and configuraiton will apply. Here is more info.

    If you are not running IIS, you can only fix this by specifying the custom error codes in IIS itself. If this is the case, hopefully your host will allow this.

    One other possibility for IIS6, would be to create custom handlers for non .net pages and files, and force them to route to asp.net, then your configuration would apply. This would not be desirable though as it could become a maintenance nightmare and additional code/configuration.

    Related SO questions:

    IIS overriding custom 404 error page in ASP.NET

    How to get Custom Error Pages working for Classic ASP with IIS 7 Integrated Pipeline

    Site not redirecting to Default Document in Classic pipeline mode

    • 0