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
We have seen that #1397 was implemented lately and we created our first API Rules v2alpha1.
However we are facing some issues when we have encoded spaces (%20) or “+” in the URL. To my understanding it should work also in these cases (correct me if I am wrong).
Description
We have seen that #1397 was implemented lately and we created our first API Rules v2alpha1.
However we are facing some issues when we have encoded spaces (%20) or “+” in the URL. To my understanding it should work also in these cases (correct me if I am wrong).
To detail more the issue we’re facing:
This is how our API Rule looks like:
It works fine for this request:
GET /Stores/NoSpaceTest 200
But it always returns 404 for the requests below:
GET /Stores/Space%20Test 404
GET /Space+Test 404
Expected result
As all the requests are under /Stores I expected all of them to match the api rule, but as I said, the two last requests fail.
Actual result
Requests with %20 return 404
Steps to reproduce
Create API Rules v2alpha1 as above and send requests containing encoded whitespaces (%20) to a valid URL
Troubleshooting
DoD [Developer & Reviewer]
The text was updated successfully, but these errors were encountered: