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

Add ability to use JSON RPC over HTTP in Wallet API #423

Closed
nesbox opened this Issue Jan 29, 2019 · 2 comments

Comments

Projects
3 participants
@nesbox
Copy link
Member

nesbox commented Jan 29, 2019

No description provided.

@nesbox nesbox self-assigned this Jan 29, 2019

@kaminskyelina kaminskyelina added the api label Feb 4, 2019

nesbox added a commit that referenced this issue Feb 5, 2019

anatolse added a commit that referenced this issue Feb 6, 2019

@nesbox nesbox added this to To do in Agile Atom 1.2 via automation Feb 6, 2019

@nesbox

This comment has been minimized.

Copy link
Member Author

nesbox commented Feb 6, 2019

added JSON RPC 2.0 over HTTP here 5414213
use --api_use_http=1 command line parameter to turn on

to test and do POST request with CURL use the following command:
curl -d '{"jsonrpc":"2.0","id":1,"method":"wallet_status"}' -H "Content-Type: application/json" -X POST http://x.x.x.x:port/api/wallet

@nesbox nesbox changed the title Do we need to move to HTTP instead TCP in the wallet API? Add ability to use JSON RPC over HTTP in Wallet API Feb 6, 2019

@nesbox nesbox moved this from To do to Done in Agile Atom 1.2 Feb 6, 2019

@gingervik gingervik assigned Sergei-Beam and unassigned nesbox Feb 6, 2019

@Sergei-Beam Sergei-Beam moved this from Done to In progress in Agile Atom 1.2 Feb 6, 2019

@Sergei-Beam Sergei-Beam moved this from In progress to Done in Agile Atom 1.2 Feb 6, 2019

@Sergei-Beam

This comment has been minimized.

Copy link
Member

Sergei-Beam commented Feb 7, 2019

Checked

@Sergei-Beam Sergei-Beam closed this Feb 7, 2019

Agile Atom 1.2 automation moved this from Done to Tested Feb 7, 2019

nesbox added a commit that referenced this issue Feb 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment