Anyone managed to get the JSON RPC server to respond? (not HTTP one)

Started by monsterer, November 28, 2014, 11:35:14 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

bytemaster

#7
December 02, 2014, 08:48:19 PM
Quote from: jsidhu on November 30, 2014, 04:46:43 PM
How do u authinticate? Or do u need to?

You authenticate by making a JSON RPC call to authenticate as the first step. 
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

jsidhu

#6
November 30, 2014, 04:46:43 PM
How do u authinticate? Or do u need to?
Hired by blockchain | Developer
delegate: dev.sidhujag

monsterer

#5
November 30, 2014, 12:20:51 PM
Quote from: bytemaster on November 28, 2014, 02:51:11 PM
Yes. 

Open up "telnet" and type in  "{"id":1,"method":"get_info","params":[]}"  and it should produce a result.

Is it a persistent connection? Any server-side push operations, like block notification?
My opinions do not represent those of metaexchange unless explicitly stated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

bytemaster

#4
November 28, 2014, 02:51:11 PM
Quote from: monsterer on November 28, 2014, 02:42:12 PM
Quote from: bytemaster on November 28, 2014, 02:00:46 PM
Http gives you json rpc at URL.  /rpc. 

The rpc port is raw tcp with pure json.  No http headers.

As in socketed TCP?

Yes. 

Open up "telnet" and type in  "{"id":1,"method":"get_info","params":[]}"  and it should produce a result.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

monsterer

#3
November 28, 2014, 02:42:12 PM
Quote from: bytemaster on November 28, 2014, 02:00:46 PM
Http gives you json rpc at URL.  /rpc. 

The rpc port is raw tcp with pure json.  No http headers.

As in socketed TCP?
My opinions do not represent those of metaexchange unless explicitly stated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

bytemaster

#2
November 28, 2014, 02:00:46 PM
Http gives you json rpc at URL.  /rpc. 

The rpc port is raw tcp with pure json.  No http headers. 
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

monsterer

#1
November 28, 2014, 11:35:14 AM
I have tried everything, but all I get is a gateway timeout error trying to authenticate with the JSON RPC API server. The HTTP one works, but not the JSON one.

Any example of this working?
My opinions do not represent those of metaexchange unless explicitly stated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads
Print
Go Up Pages1
User actions