Re: Handle Errors with Url Routing

2009-02-16 Thread eyal
Also forgot to mention that I have a 404.vm file in the rescues folder. If the url is tempered I understand that the message in the 404 file should be displayed. But instead I get an error: The resource cannot be found. Description: HTTP 404. The resource you are looking for Any suggestions?

Re: Handle Errors with Url Routing

2009-02-16 Thread Ricardo Lopes
The default web.config customerrors should apply even if you use routing. http://msdn.microsoft.com/en-us/library/h0hfz6fc.aspx 2009/2/16 eyal ebarda...@gmail.com Also forgot to mention that I have a 404.vm file in the rescues folder. If the url is tempered I understand that the message in

Re: Handle Errors with Url Routing

2009-02-12 Thread eyal
That is exactly what I'm trying to get the RoutingRule class to do but without any success. I tried to use RedirectToAction(404) or RedirectToAction (generalerror) using Try Catch. I am getting the following error: The resource cannot be found. Description: HTTP 404. The resource you are

Handle Errors with Url Routing

2009-02-11 Thread eyal
Hi there, when defining routing pattern rules you can specify type of parameter as such .Restrict(Id).ValidInteger But what if someone tempers with the url and changes the parameter value to a non integer. How can you handle this? For example: mysite.com/productName/12 - correct url

Re: Handle Errors with Url Routing

2009-02-11 Thread Ken Egozi
it won't reach the controller since the route won't match. this should be dealt like any other 404 error On Thu, Feb 12, 2009 at 6:52 AM, eyal ebarda...@gmail.com wrote: Hi there, when defining routing pattern rules you can specify type of parameter as such .Restrict(Id).ValidInteger But