helo,
I have an `HttpClient` that I use to make requests to different IP addresses. I also set a host-header for these requests which is the same for all IPs. Before vertx 3.4, it worked as expected, the requests would reach different IPs with the same hostheader and there was at least one connection to each IP, managed by the connection pool. Since vertx 3.4 however, only one connection (to the first IP) is established, and subsequent requests always use that connection.
I had a look in the vertx code and think it is because before vertx 3.4, the `ConnectionManager` was pooling connection based on `TargetAddress` and since 3.4 it is pooling connections based on a `ConnectionKey` which only includes the `peerHost` (i.e. the host header if set). That means there is only one ConnectionQueue per hostname (as set in the host-header), even if requests to different IPs are made.
Am I understanding it correctly and if so, why was this change made in vertx 3.4?
thanks,
Josef