07-02-05

1. W E D N E S D A Y , A P R I L 1 0 , 2 0 1 3
Handling 404 Error in ASP.NET MVC
In ASP.NET Web Forms, handling 404 errors are easy - which is basically a web.config setting. In
ASP.NET MVC, it is a bit more complicated. Why is it more complicated? In comparison, everything
is seemingly easier in MVC than WebForm.
It is more complicated mainly because of Routing. In WebForm, most 404 occurs because of non-
existent file and each UR: is usually mapped to a particular file (aspx). With MVC, that is not the
case. All requests are handled by the Routing table and based on that it will invoke appropriate
controller and actions etc. Secondly, our basic default route usually is quite common
({controller}/{action}/{id}) - therefore most URL request will be caught by this route.
So, let's dive in on how can we do proper handling of 404 errors with ASP.NET MVC.
TURN ON CUSTOM ERROR IN WEB.CONFIG
1. <customErrors mode="On" defaultRedirect="~/Error/Error">
2. <error statusCode="404" redirect="~/Error/Http404" />
3. </customErrors>
DECLARE DETAIL ROUTES MAPPED IN ROUTE TABLE
So instead of just using the default route:
1. routes.MapRoute(
2. name: "Default",
3. url: "{controller}/{action}/{id}",
4. defaults: new { controller = "Home", action = "Index", id =
UrlParameter.Optional }
5. );
Declare all your intended route explicitly and create a "catch-all" to handle non-matching route -
which basically a 404. In MVC, a 404 can happen when you try to access a URL where the there is
no controller for. This code in the routing table handles that scenario.
1. routes.MapRoute(

2. 2. name: "Account",
3. url: "Account/{action}/{id}",
4. defaults: new { controller = "Account", action = "Index", id =
UrlParameter.Optional }
5. );
6.
7. routes.MapRoute(
8. name: "Home",
9. url: "Home/{action}/{id}",
10. defaults: new { controller = "Home", action = "Index", id =
UrlParameter.Optional }
11. );
12.
13. routes.MapRoute(
14. name: "Admin",
15. url: "Admin/{action}/{id}",
16. defaults: new { controller = "Admin", action = "Index", id =
UrlParameter.Optional }
17. );
18.
19. routes.MapRoute(
20. name: "404-PageNotFound",
21. url: "{*url}",
22. defaults: new { controller = "Home", action = "Http404" }
23. );
OVERRIDE HANDLEUNKNOWNACTION IN BASECONTROLLER CLASS
Create a Controller base class that every controller in your application inherits from. In that base
controller class, override HandleUnknownAction method. Now, another scenario that a 404 may
happen is that when the controller exists, but there is no action for it. In this case, the routing
table will not be able to trap it easily - but the controller class has a method that handle that.
1. [AllowAnonymous]
2. public class ErrorController : Controller
3. {
4. protected override void HandleUnknownAction(string actionName)
5. {
6. if (this.GetType() != typeof(ErrorController))
7. {
8. var errorRoute = new RouteData();
9. errorRoute.Values.Add("controller", "Error");
10. errorRoute.Values.Add("action", "Http404");

3. 11. errorRoute.Values.Add("url",
HttpContext.Request.Url.OriginalString);
12.
13. View("Http404").ExecuteResult(this.ControllerContext);
14. }
15. }
16.
17. public ActionResult Http404()
18. {
19. return View();
20. }
21.
22. public ActionResult Error()
23. {
24. return View();
25. }
26. }
CREATE CORRESPONDING VIEWS
View for generic error: Error.chtml
1. @model System.Web.Mvc.HandleErrorInfo
2.
3. @{
4. ViewBag.Title = "Error";
5. }
6.
7. <hgroup class="title">
8. <h1 class="error">Error.</h1>
9. <br />
10. <h2 class="error">An error occurred while processing your request.</h2>
11. @if (Request.IsLocal)
12. {
13. <p>
14. @Model.Exception.StackTrace
15. </p>
16. }
17. else
18. {
19. <h3>@Model.Exception.Message</h3>
20. }
21. </hgroup>
View for 404 error: Http404.chtml

4. 1. @model System.Web.Mvc.HandleErrorInfo
2.
3. @{
4. ViewBag.Title = "404 Error: Page Not Found";
5. }
6. <hgroup class="title">
7. <h1 class="error">We Couldn't Find Your Page! (404 Error)</h1><br />
8. <h2 class="error">Unfortunately, the page you've requested cannot be
displayed. </h2><br />
9. <h2>It appears that you've lost your way either through an outdated link <br
/>or a typo on the page you were trying to reach.</h2>
10. </hgroup>