-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bad request returned for percent-encoded get_by_attribute #195
Comments
The short problem description is Let's talk about the details. The incoming request has URI value Standart HTTP lib reads the request and makes the first unescape approach. On this step, the URI changed to It sees the I hope the Fast and in some way a dirty hack is using double parameter escaping in case it contains Also, the testcases should be updated to use the latest REST gate version for tests. Actual is |
We can't solve it at the moment, dependencies need to be fixed and updated. |
Associated test case will be removed for now. |
BTW, have you looked at https://github.com/labstack/echo/blob/447c92d842e2f91c07eb032f619bea212beeee60/echo.go#L951? It's supposed to be using |
In fact, this change to
but it's a huge can of worms: which was flipped back and forth already: |
Maybe it's worth trying |
⬆️ can be tried now that we have Go 1.22+ required anyway. |
|
Closes #195. Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
Closes #195. Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
While what we want to do here is perfectly fine as per HTTP specification, we can't fit this into our current stack. If something changes in libraries we can return to this problem, but for now it's WONTFIX. |
The case itself is not that popular, btw, so this is a minor limitation. And one can always search/fetch by oid if needed. |
Current Behavior
https://rest.fs.neo.org/7ZVSQHtioVRiDT2btN9xEmQhczXV9vryCEAHUawfD8Sc/7-1712215152/index.html#suites/4f5ca4977289636df3b53e1debc15dcf/84697d2930280bd1/
Expected Behavior
No error, the URL seems to be fine here.
The text was updated successfully, but these errors were encountered: