-
Hi guys. I discovered strange and different routing behavior between versions Expected BehaviorIn version {
"DownstreamPathTemplate": "/{tenantId}/products?{everything}",
"UpstreamPathTemplate": "/{tenantId}/products?{everything}",
"UpstreamHttpMethod": [ "Get" ]
},
{
"DownstreamPathTemplate": "/{tenantId}/products/{everything}",
"UpstreamPathTemplate": "/{tenantId}/products/{everything}",
"UpstreamHttpMethod": [ "Get" ]
}, When I call a request GET localhost/1/products/1 then the correct route Actual BehaviorIn version Specifications
Maybe this PR? #748 Any idea for a quick fix on my part? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Eliminate the initial redundant route as it is inherently included in the subsequent Catch All route. It should be one route only {
"DownstreamPathTemplate": "/{tenantId}/products/{everything}", // all query strings are included
"UpstreamPathTemplate": "/{tenantId}/products/{everything}",
"UpstreamHttpMethod": [ "Get" ]
}, Also, note that if no Priority is defined, then the first matching route prevails! This explains the odd behavior observed. |
Beta Was this translation helpful? Give feedback.
-
@Burgyn Hello Miňo! |
Beta Was this translation helpful? Give feedback.
Eliminate the initial redundant route as it is inherently included in the subsequent Catch All route.
It should be one route only
Also, note that if no Priority is defined, then the first matching route prevails! This explains the odd behavior observed.