When there are mix use of default webService and regexPath webService, the default webService may get biased and its route won't get selected.
with 2 webService setup like this:
one with default routes (empty Path, or rootPath '/')
one with regex Path
during detectWebService, computeWebserviceScore, with a request trying to hit the default route.
defaultRoute would always get score 0
and regexPath would always get score 1 (regex not match)
this would select wrong webService 100%, and won't find the correct route.
since I have fix on this part with issue #547 and PR #549 , I would image the fix is remove the default score for any regex routeToken, but that would definitely be a breaking change.
When there are mix use of default webService and regexPath webService, the default webService may get biased and its route won't get selected.
with 2 webService setup like this:
since I have fix on this part with issue #547 and PR #549 , I would image the fix is remove the default score for any regex routeToken, but that would definitely be a breaking change.
reproduce, also here is go playground link: https://go.dev/play/p/xbpUnvAETio