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 <[email protected]> wrote: > > 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 > mysite.com/productName/d <- erroneous url > mysite.com/productName/ <- erroneous url > > Normally, I trap and handle such errors in a Controller. But now that > I'm using routing, such errors for some reason dont even reach the > controller. > > thanks > > eyal > > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.delver.com http://www.musicglue.com http://www.castleproject.org http://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
