cursor in /claimable_balances not validated #3085
Milestone
Comments
7 tasks
abuiles
added a commit
to abuiles/go
that referenced
this issue
Oct 2, 2020
We do cursor validation, however, if there is an error we return a plain error instead of a `problem.P` -- this causes horizon to handle the error as a 500 instead of a 400. This fix moves cursor parsing to its own method and then use it in the query handler to return a `problem.P` error. Fixes stellar#3085.
abuiles
added a commit
that referenced
this issue
Oct 2, 2020
We do cursor validation, however, if there is an error we return a plain error instead of a `problem.P` -- this causes horizon to handle the error as a 500 instead of a 400. This fix moves cursor parsing to its own method and then use it in the query handler to return a `problem.P` error. Fixes #3085.
|
Fixed in #3088 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version are you using?
1.9.0
What did you do?
Request
/claimable_balanceswith invalidcursorvalue. Ex: https://horizon-testnet.stellar.org/claimable_balances?cursor=1003529-00000043d380c38a2f2cac46ab63674064c56fdce6b977fdef1a278ad50e1a7e6a5e18 (hex-encoded balance id is malformed).What did you expect to see?
400 Bad Requestresponse.What did you see instead?
500 Internal Server Errorresponse.The text was updated successfully, but these errors were encountered: