Skip to content

Incorrect routing when the query parameter is in the configuration #2065

Answered by raman-m
Burgyn asked this question in Q&A
Discussion options

You must be logged in to vote

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.

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@raman-m
Comment options

@raman-m
Comment options

@raman-m
Comment options

Answer selected by raman-m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
Routing Ocelot feature: Routing
2 participants
Converted from issue

This discussion was converted from issue #2064 on May 10, 2024 14:34.