Constraint Score matches Normal Capture Node and picks wrong route.

Fix for #1412

A URL that matches both the constraint and the normal capture node produces the same score, so it takes the first which happens to be the normal capture node. 

Increased the Constraint score to 2000 to fix the issue.