views:

23

answers:

1

If I have a route like this:

routes.Add(new Route("{controller}/{page}", 
    new RouteValueDictionary
    {
        { "page", UrlParameter.Optional }
    },
    new RouteValueDictionary
    {
        { "page", @"[Pp]age\d+" }
    }, 
    new MvcRouteHandler()
));

Then the route doesn't match when {page} is missing, however if I remove the constraint it matches. Is this a bug or a feature?

A: 

It's a feature: how can the constraint match if the parameter if optional? You might either want to set the default value for "page" to "Page1" to resolve your problem, or replace your regex with "([Pp]age\d+)?" to allow nothing to match (I'm not sure about this one and can't test it atm).

Julien Lebosquain
Thanks, setting a default value instead of UrlParameter.Optional did the trick. Changing the regexp didn't work.
ciscoheat