lighthouse/beacon_node/http_api/tests
Mac L 41b5af9b16 Support IPv6 in BN and VC HTTP APIs (#3104)
## Issue Addressed

#3103

## Proposed Changes

Parse `http-address` and `metrics-address` as `IpAddr` for both the beacon node and validator client to support IPv6 addresses.
Also adjusts parsing of CORS origins to allow for IPv6 addresses.

## Usage
You can now set  `http-address` and/or `metrics-address`  flags to IPv6 addresses.
For example, the following:
`lighthouse bn --http --http-address :: --metrics --metrics-address ::1`
will expose the beacon node HTTP server on `[::]` (equivalent of `0.0.0.0` in IPv4) and the metrics HTTP server on `localhost` (the equivalent of `127.0.0.1` in IPv4) 

The beacon node API can then be accessed by:
`curl "http://[server-ipv6-address]:5052/eth/v1/some_endpoint"`

And the metrics server api can be accessed by:
`curl "http://localhost:5054/metrics"` or by `curl "http://[::1]:5054/metrics"`

## Additional Info
On most Linux distributions the `v6only` flag is set to `false` by default (see the section for the `IPV6_V6ONLY` flag in https://www.man7.org/linux/man-pages/man7/ipv6.7.html) which means IPv4 connections will continue to function on a IPv6 address (providing it is appropriately mapped). This means that even if the Lighthouse API is running on `::` it is also possible to accept IPv4 connections.

However on Windows, this is not the case. The `v6only` flag is set to `true` so binding to `::` will only allow IPv6 connections.
2022-03-24 00:04:49 +00:00
..
common.rs Support IPv6 in BN and VC HTTP APIs (#3104) 2022-03-24 00:04:49 +00:00
fork_tests.rs Refactor Peerdb and PeerManager (#2660) 2021-10-11 02:45:06 +00:00
interactive_tests.rs Refactor Peerdb and PeerManager (#2660) 2021-10-11 02:45:06 +00:00
main.rs Fix chain_id value in config/deposit_contract RPC method (#2659) 2021-10-01 06:32:38 +00:00
tests.rs Allow proposer duties request for the next epoch (#2963) 2022-02-18 05:32:00 +00:00