Hi folks,
Is it possible to create a final route that catches all .. and bounces the user to a 404 view in ASP.NET MVC?
NOTE: I don't want to set this up in my IIS settings.
views:
4231answers:
2
+9
A:
Found the answer myself.
Richard Dingwall has an excellent post going through various strategies. I particularly like the FilterAttribute solution. I'm not a fan of throwing exceptions around willy nilly, so i'll see if i can improve on that :)
For the global.asax, just add this code as your last route to register:
routes.MapRoute(
"404-PageNotFound",
"{*url}",
new { controller = "StaticContent", action = "PageNotFound" }
);
Pure.Krome
2008-11-22 00:38:32
I've tried this, but it doesn't work. I have put the route under my default route, but i still get 404 errors.
Martijn
2009-04-09 12:48:36
Hmm. i think it works for me.
Pure.Krome
2009-04-09 14:58:46
Can you please explain what exactly I have to assuming I am very new to MVC.
Tanmoy
2009-06-16 12:57:53
2 things. a) add that last route to your route list. b) create a controller (in my example, i called it StaticContentController) with an Action method (in my example, i added a method called PageNotFound(..)) add logic this method to display the 404 page not found, View.
Pure.Krome
2009-06-17 03:08:52
If you still have the default route (I.E. {controller}/{action}/{id}) in RegisterRoutes() it will trap all URLs that match the format of a normal MVC request.In other words the catch-all route can only intercept a bad URL if it doesn't fit the normal format (**blah/blah/blah/blah**). In the case of a non-existent controller the exception must be handled through conventional ASP.NET handling.Theres a good description of handling at http://stackoverflow.com/questions/619895/how-can-i-properly-handle-404s-in-asp-net-mvc/620559#620559
RonnBlack
2009-07-14 01:38:44
Indeed the 'catch all' is maybe not the best approach. Feedback on this answer pls: http://stackoverflow.com/questions/619895/how-can-i-properly-handle-404s-in-asp-net-mvc/2577095#2577095
cottsak
2010-04-05 06:19:09
A:
This might be a problem when you use
throw new HttpException(404);
When you want to catch that, I don't know any other way then editing your web config.
Paco
2008-11-22 19:46:01
What if the exception is not thrown by a controller action? I throw a 404 in my controller factory.
Paco
2008-11-23 13:38:48
Not sure then - i'm not playing around with controller factories. soz.
Pure.Krome
2009-04-09 14:59:51
Controllerfactory is not the only place where it can happen. I map a catch all route to an actionmethod that just throws the exception. The exception is handled by the web.config
Paco
2009-04-09 17:52:20