In what area(s)?
/area runtime
What version of Dapr?
Runtime 1.5.1, 1.4.3
Expected Behavior
- Method invocation with URL that contains a urlencoded
/ character that is %2F:
http://localhost:[DAPR_PORT]/v1.0/invoke/[MY_SERVICE]/method/test/value%2F123
- Expected ASP.Core service endpoint to be called from the sidecar:
/test/value%2F123
Actual Behavior
- Method invocation with URL that contains a urlencoded
/ character that is %2F:
http://localhost:[DAPR_PORT]/v1.0/invoke/[MY_SERVICE]/method/test/value%2F123
- Actual ASP.Core service endpoint called from the sidecar:
/test/value/123
Notes
When calling the ASP.Core service endpoint directly, the route matches the expected /test/value%2F123. When doing method invocation through Dapr, Dapr seems to be automatically decoding %2F thus modifying the expected path.
In what area(s)?
What version of Dapr?
Runtime 1.5.1, 1.4.3
Expected Behavior
/character that is%2F:http://localhost:[DAPR_PORT]/v1.0/invoke/[MY_SERVICE]/method/test/value%2F123/test/value%2F123Actual Behavior
/character that is%2F:http://localhost:[DAPR_PORT]/v1.0/invoke/[MY_SERVICE]/method/test/value%2F123/test/value/123Notes
When calling the ASP.Core service endpoint directly, the route matches the expected
/test/value%2F123. When doing method invocation through Dapr, Dapr seems to be automatically decoding%2Fthus modifying the expected path.