infra/proxyd/integration_tests/testdata/ws.toml

whitelist_error_message = "rpc method is not whitelisted"

ws_backend_group = "main"

ws_method_whitelist = [
  "eth_subscribe",
  "eth_accounts"
]

[server]
rpc_port = 8545
ws_port = 8546

[backend]
response_timeout_seconds = 1

[backends]
[backends.good]
rpc_url = "$GOOD_BACKEND_RPC_URL"
ws_url = "$GOOD_BACKEND_RPC_URL"
max_ws_conns = 1

[backend_groups]
[backend_groups.main]
backends = ["good"]

[rpc_method_mappings]
eth_chainId = "main"
proxyd: Add customizable whitelist error message (#3544) * proxyd: Add customizable whitelist error message Alchemy is asking for this so that we can include their affiliate link. * add missing test case * fix error message * goimports 2022-09-23 23:21:12 +03:00			`whitelist_error_message = "rpc method is not whitelisted"`

proxyd: Fix concurrent WS write panic (#2711) Fixes a panic in the websocket proxyd logic. Normally, the `clientPump` and `backendPump` methods in `WSProxier` send data in one direction. However, when the client sends an invalid RPC, the `clientPump` will send a response _directly to the client_ in order to avoid unnecessary roundtrips to the backend. This could be interleaved with concurrent writes to the client's WS in `backendPump`, and would cause a panic in the WS library. To test this, this PR includes a dedicated integration test that reliably triggers the issue. In addition, this PR adds additional testing for WS functionality. 2022-06-08 18:09:32 +03:00			`ws_backend_group = "main"`

			`ws_method_whitelist = [`
proxyd: Use canned response for eth_accounts (#2801) We never want to expose Geth's accounts to the public internet, so proxyd will now return `[]` for `eth_accounts` RPC calls without hitting the backend. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> 2022-06-16 22:02:39 +03:00			`"eth_subscribe",`
			`"eth_accounts"`
proxyd: Fix concurrent WS write panic (#2711) Fixes a panic in the websocket proxyd logic. Normally, the `clientPump` and `backendPump` methods in `WSProxier` send data in one direction. However, when the client sends an invalid RPC, the `clientPump` will send a response _directly to the client_ in order to avoid unnecessary roundtrips to the backend. This could be interleaved with concurrent writes to the client's WS in `backendPump`, and would cause a panic in the WS library. To test this, this PR includes a dedicated integration test that reliably triggers the issue. In addition, this PR adds additional testing for WS functionality. 2022-06-08 18:09:32 +03:00			`]`

			`[server]`
			`rpc_port = 8545`
			`ws_port = 8546`

			`[backend]`
			`response_timeout_seconds = 1`

			`[backends]`
			`[backends.good]`
			`rpc_url = "$GOOD_BACKEND_RPC_URL"`
			`ws_url = "$GOOD_BACKEND_RPC_URL"`
			`max_ws_conns = 1`

			`[backend_groups]`
			`[backend_groups.main]`
			`backends = ["good"]`

			`[rpc_method_mappings]`
			`eth_chainId = "main"`