-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect Routing when a configuration exists with query param wildcard #2132
Comments
Thanks for reporting this! Are you C# developer? |
Thanks, Yes C# developer. |
Could you look into the issue by debugging the solution and examining Ocelot's code when you have some spare time, please? |
@lelloz0 Hello Raffaele,
Why did you delete your comment from issue #2132?
Please be aware that using wildcards is not supported in Ocelot templates or placeholders.
If you encounter any unusual behavior with special characters, please let us know.
|
I realized the issue is indeed somewhere else and not related to the wildcards. Thanks for the follow up! |
@pwshfan, okay, we will concentrate on the originally reported bug. Feel free to report any issues, but please create new ones. |
@int0x81, welcome to your assignment! |
Ocelot now matches routes incorrectly.
This started breaking between versions 22.0.1 and 23.0.0.
If I have two configurations -
Now if I initiate a call with
/api/v1/abc2/apple?isRequired=1
Expected Route:
{Endpoint2}/api/v1/apple?isRequired=1
Actually Routes to:
{Endpoint1}/api/v1/abc?isRequired=1"
Similar issue reported in: Originally posted by @Burgyn in #2065
The text was updated successfully, but these errors were encountered: