diff options
| author | Marius Kjærstad <sandakersmann@users.noreply.github.com> | 2018-12-02 20:03:31 +0800 |
|---|---|---|
| committer | Martin Holst Swende <martin@swende.se> | 2018-12-02 20:03:31 +0800 |
| commit | f850123ec7500af732b73c2501f1ef36d80ee01d (patch) | |
| tree | 7dcb6b603f394db6a6cd5ee792b7261acf891126 | |
| parent | efe5886877d3f171fae5adfd1e5f1c585e16946b (diff) | |
| download | dexon-f850123ec7500af732b73c2501f1ef36d80ee01d.tar.gz dexon-f850123ec7500af732b73c2501f1ef36d80ee01d.tar.zst dexon-f850123ec7500af732b73c2501f1ef36d80ee01d.zip | |
Changed http:// to https:// on JSON-RPC link (#18224)
Changed http:// to https:// on JSON-RPC link in README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -168,7 +168,7 @@ HTTP based JSON-RPC API options: * `--ipcpath` Filename for IPC socket/pipe within the datadir (explicit paths escape it) You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect -via HTTP, WS or IPC to a Geth node configured with the above flags and you'll need to speak [JSON-RPC](http://www.jsonrpc.org/specification) +via HTTP, WS or IPC to a Geth node configured with the above flags and you'll need to speak [JSON-RPC](https://www.jsonrpc.org/specification) on all transports. You can reuse the same connection for multiple requests! **Note: Please understand the security implications of opening up an HTTP/WS based transport before |