Skip to content
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

RPC recoverwallet returns error and Unknown message with Status code: OK #11564

Closed
wieslawsoltes opened this issue Sep 24, 2023 · 1 comment · Fixed by #11603
Closed

RPC recoverwallet returns error and Unknown message with Status code: OK #11564

wieslawsoltes opened this issue Sep 24, 2023 · 1 comment · Fixed by #11603
Assignees

Comments

@wieslawsoltes
Copy link
Collaborator

General Description

RPC recoverwallet returns error and Unknown message with Status code: OK with invalid input data.

How To Reproduce?

RequestBody:

{"method":"recoverwallet","params":["Wallet","1",""],"jsonrpc":"2.0","id":"1"}

Status code: OK
Response body:

{"jsonrpc":"2.0","error":{"code":-32603,"message":"Unknown"},"id":"1"}

Screenshots

Operating System

Please consider your privacy, before completing this section.

Example: linuxmint 21.2

Logs

Wasabi Version

master

@lontivero lontivero self-assigned this Sep 26, 2023
@lontivero
Copy link
Collaborator

lontivero commented Sep 26, 2023

I've been trying to find some specifications for JSON-RPC over HTTP but I couldn't find anything really concrete. There are some people suggesting some mapping between JSON-RPC error codes and HTTP status code but that's problematic for batch requests because in case you send a two-requests batch and one succeeded while the other failed, which is the real appropriated HTTP status code?

These documents seems to be two contradictory proposals:

There is also a lot of discussions around the topic in the json-rpc specs discussion group: https://groups.google.com/g/json-rpc/search?q=http%20status%20code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants