Skip to content
This repository has been archived by the owner on Aug 8, 2018. It is now read-only.

RPCClient https support #163

Closed
utzig opened this issue Aug 15, 2016 · 1 comment
Closed

RPCClient https support #163

utzig opened this issue Aug 15, 2016 · 1 comment

Comments

@utzig
Copy link

utzig commented Aug 15, 2016

When creating a new eth RPC connection, the JSONRPCClient receives a host and port from which a new http connection URL is created here:

https://github.com/ethereum/pyethapp/blob/develop/pyethapp/rpc_client.py#L121

This works with most eth clients (eg geth) but may be a limitation in other cases. For example, using https://morden.infura.io as backend does not work (because http is not supported).
@utzig utzig changed the title No support for RPC backends that are not running over http RPCClient https support Aug 15, 2016
@utzig utzig mentioned this issue Aug 17, 2016
Merged
@konradkonrad
Copy link

will be resolved in upcoming release (see #166)

konradkonrad added a commit that referenced this issue Aug 22, 2016
@konradkonrad
Bump version: 1.4.0 → 1.5.0
e771736 
Changelog:
- added OR event filter support in `JSONRPCClient` #160 #168 #149
- add ssl-protocol option to `JSONRPCClient` #166 #163
- add content-type header to `JSONRPCClient` #165 #164
- fix license documentation in `setup.py` #167
- bugfix for exception import regression #158 #157
- add check for OOG on `deploy_solidity_contract` #151
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@utzig @konradkonrad