You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specified placeholder variable value should be replaced within the Downstream URI provided in the UpstreamPathTemplate and DownStreamPathTemplate. For instance,
When the request URI is http://localhost:5001/v1/subscriptions(123)/updates
Then the downstream request URI should be http://localhost:50110/api/subscriptions(123)/updates
Actual Behavior
It's adding extra round braces ) in the Downstream request. It's a clear issue of replacing placeholder variables.
When the request URI is http://localhost:5001/v1/subscriptions(123)/updates
Then the downstream request URI is http://localhost:50110/api/subscriptions(123))/updates
Steps to Reproduce the Problem
Add a route with the placeholder within the round braces
Get parameter value in the downstream. Observed the value received at the downstream application.
NOTE: An issue is not with specific round braces. It reproduces with any other routes where the placeholder does not exactly(eg. /{id}/ ) provide between slashes.
Specifications
Version: 17.0.0
Platform: .NET 5
The text was updated successfully, but these errors were encountered:
@PratikPatel-Mtech Looks like this is from Microsoft aspnet inbuilt thing for Placeholder Value comming through HttpContext.
But its really strange to note that from swagger for these routes we get right result.
probably swagger can implement this as it has UI for input, but from postman its tough to find any specific pattern. Example from swagger /su((!))/row is valid for route /su({string}/row
We will check this... Too busy...
Do you have intention to write unit tests or acceptance one in your fork?
Please, fork Ocelot repo and in some feature branch you can write tests...
By this way you will confirm that the bug still exists in current version 20.0
Expected Behavior
The specified placeholder variable value should be replaced within the Downstream URI provided in the UpstreamPathTemplate and DownStreamPathTemplate. For instance,
Route Configurations:
When the request URI is
http://localhost:5001/v1/subscriptions(123)/updates
Then the downstream request URI should be
http://localhost:50110/api/subscriptions(123)/updates
Actual Behavior
It's adding extra round braces
)
in the Downstream request. It's a clear issue of replacing placeholder variables.When the request URI is
http://localhost:5001/v1/subscriptions(123)/updates
Then the downstream request URI is
http://localhost:50110/api/subscriptions(123))/updates
Steps to Reproduce the Problem
NOTE: An issue is not with specific round braces. It reproduces with any other routes where the placeholder does not exactly(eg.
/{id}/
) provide between slashes.Specifications
The text was updated successfully, but these errors were encountered: