5 Commits (576681f29b895dd39e559b7ba17fcd89b42e4833)

Author	SHA1	Message	Date
Antoine Toulme	f59ed3565d	graphql: always return 400 if errors are present in the response (#21882) ... * Make sure to return 400 when errors are present in the response * graphql: use less memory in chainconfig for tests Co-authored-by: Martin Holst Swende <martin@swende.se>	4 years ago
rene	c0c01612e9	node: refactor package node (#21105) ... This PR significantly changes the APIs for instantiating Ethereum nodes in a Go program. The new APIs are not backwards-compatible, but we feel that this is made up for by the much simpler way of registering services on node.Node. You can find more information and rationale in the design document: https://gist.github.com/renaynay/5bec2de19fde66f4d04c535fd24f0775. There is also a new feature in Node's Go API: it is now possible to register arbitrary handlers on the user-facing HTTP server. In geth, this facility is used to enable GraphQL. There is a single minor change relevant for geth users in this PR: The GraphQL API is no longer available separately from the JSON-RPC HTTP server. If you want GraphQL, you need to enable it using the ./geth --http --graphql flag combination. The --graphql.port and --graphql.addr flags are no longer available.	4 years ago
rene	07d909ff32	node: allow websocket and HTTP on the same port (#20810) ... This change makes it possible to run geth with JSON-RPC over HTTP and WebSocket on the same TCP port. The default port for WebSocket is still 8546. geth --rpc --rpcport 8545 --ws --wsport 8545 This also removes a lot of deprecated API surface from package rpc. The rpc package is now purely about serving JSON-RPC and no longer provides a way to start an HTTP server.	5 years ago
rene	d7851e6359	graphql, node, rpc: fix typos in comments (#20824)	5 years ago
Péter Szilágyi	e3ec77f50e	cmd, graphql, node: graphql flag polishes, les integration	5 years ago