Like the comment said that's a way to add a route constraint. But this doesn't seem to be the right thing unless you plan to have two separate actions that deal with movies/byselected
for example:
movies/byselected/{MovieName}
and movies/byselected/{year}/{month}
Here is the warning from the relevant microsoft doc:
```
Warning
Avoid using constraints for input validation, because doing so means that invalid input will result in a 404 (Not Found) instead of a 400 with an appropriate error message. Route constraints should be used to disambiguate between similar routes, not to validate the inputs for a particular route.
```
Also - there is a much nicer syntax for constraints:
In MVC5 you can use attribute routes and then you can use the inline constraint syntax, but at this point in time you should probably look at MVC core. You can spec:
"movies/BySelected/{year:length(4)}/{month:length(2)}