Optional routing parameter with constraint in ASP.NET MVC 2?

Question

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?

jtlowe · Accepted Answer · 2013-06-24 22:22:51Z

9

I'm using ^$| within a regex, such as: (^$|[Pp]age\d+). I found this question while searching for an answer to this and figured I'd add what I found here.

routes.MapRoute(
  name: "News Archive",
  url: "News/{page}",
  defaults: new { controller = "news", action = "List", page= UrlParameter.Optional },
  constraints: new { page= @"^$|[0-9][0-9]" });

answered Jun 24, 2013 at 22:22

jtlowe

8571 gold badge8 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Julien Lebosquain · Accepted Answer · 2010-08-12 13:34:16Z

7

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).

answered Aug 12, 2010 at 13:34

Julien Lebosquain

41.4k9 gold badges108 silver badges120 bronze badges

1 Comment

ciscoheat Over a year ago

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

Collectives™ on Stack Overflow

Optional routing parameter with constraint in ASP.NET MVC 2?

2 Answers 2

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related