Asp – Missing aspx page is causing a global exception instead of redirecting to 404 page

asp.net

I have a global exception handler in global.asax.cs file in the Application_Error handler which redirects to the error.aspx page.
I also have the customError section in my web.config file. When I request a non existing aspx page, the 404.aspx file is NOT shown and the Application_Error handler is fired.

I was expecting 404.aspx to be shown.

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

Best Answer

Are you viewing the website locally? Because if locally then you'll see an error page since you have the mode set to RemoteOnly. Set mode="On" and see if you get the 404.aspx page.

Related Solutions

Best way to implement a 404 in ASP.NET

Handle this in your Global.asax's OnError event:

protected void Application_Error(object sender, EventArgs e){
  // An error has occured on a .Net page.
  var serverError = Server.GetLastError() as HttpException;

  if (serverError != null){
    if (serverError.GetHttpCode() == 404){
      Server.ClearError();
      Server.Transfer("/Errors/404.aspx");
    }
  }
}

In you error page, you should ensure that you're setting the status code correctly:

// If you're running under IIS 7 in Integrated mode set use this line to override
// IIS errors:
Response.TrySkipIisCustomErrors = true;

// Set status code and message; you could also use the HttpStatusCode enum:
// System.Net.HttpStatusCode.NotFound
Response.StatusCode = 404;
Response.StatusDescription = "Page not found";

You can also handle the various other error codes in here quite nicely.

Google will generally follow the 302, and then honour the 404 status code - so you need to make sure that you return that on your error page.

Asp – Uploading website to webhost, webconfig Runtime error

Usually this happens if an unhandled exception occurs in the code.

Seeing how you are having problems configuring the web.config to allow the website to show you the error and stack trace remotely,

you could adding TRY and CATCH blocks around parts of the code where you suspect the exception could be thrown... Then on catch you can do a redirect to a generic simple error page where you can display the exception's message.

Edit: you can also try redirecting to a custom error page from the on error event in global.

Best Answer

Related Solutions

Best way to implement a 404 in ASP.NET

Asp – Uploading website to webhost, webconfig Runtime error

Related Topic