Implementing a Custom Error page on an ASP.Net website

asp.netcustom-error-pagescustom-errorsweb.config

I have an ASP.Net website and I want to use a custom error page. I put the following code in my web.config

<customErrors mode="On" defaultRedirect="~/error.aspx">
    <error statusCode="404" redirect="~/error.aspx" />
</customErrors>

The problem is when i go to a URL that does not exist is still uses the 404 error page specified in IIS Manager.

Question: How can I make it use the error.aspx page I have created? Why do the settings in IIS Manager override the web.config?

Best Answer

Try this way, almost same.. but that's what I did, and working.

<configuration>
    <system.web>
       <customErrors mode="On" defaultRedirect="apperror.aspx">
          <error statusCode="404" redirect="404.aspx" />
          <error statusCode="500" redirect="500.aspx" />
       </customErrors>
    </system.web>
</configuration>

or try to change the 404 error page from IIS settings, if required urgently.

Related Solutions

Asp.net-mvc – ASP.NET MVC HandleError

[HandleError]

When you provide only the HandleError attribute to your class (or to your action method for that matter), then when an unhandled exception occurs MVC will look for a corresponding View named "Error" first in the Controller's View folder. If it can't find it there then it will proceed to look in the Shared View folder (which should have an Error.aspx file in it by default)

[HandleError(ExceptionType = typeof(SqlException), View = "DatabaseError")]
[HandleError(ExceptionType = typeof(NullReferenceException), View = "LameErrorHandling")]

You can also stack up additional attributes with specific information about the type of exception you are looking for. At that point, you can direct the Error to a specific view other than the default "Error" view.

For more information, take a look at Scott Guthrie's blog post about it.

Asp.net-mvc – Routing for custom ASP.NET MVC 404 Error page

I've tried to enable custom errors on production server for 3 hours, seems I found final solution how to do this in ASP.NET MVC without any routes.

To enable custom errors in ASP.NET MVC application we need (IIS 7+):

Configure custom pages in web config under system.web section:
```
<customErrors mode="RemoteOnly"  defaultRedirect="~/error">
    <error statusCode="404" redirect="~/error/Error404" />
    <error statusCode="500" redirect="~/error" />
</customErrors>
```
RemoteOnly means that on local network you will see real errors (very useful during development). We can also rewrite error page for any error code.

Set magic Response parameter and response status code (in error handling module or in error handle attribute)

  HttpContext.Current.Response.StatusCode = 500;
  HttpContext.Current.Response.TrySkipIisCustomErrors = true;

Set another magic setting in web config under system.webServer section:
```
<httpErrors errorMode="Detailed" />
```

This was final thing that I've found and after this I can see custom errors on production server.

Best Answer

Related Solutions

Asp.net-mvc – ASP.NET MVC HandleError

Asp.net-mvc – Routing for custom ASP.NET MVC 404 Error page

Related Topic