0
Files
src/net
David Benjamin 13072a47ac Use HostResolverEndpointResults in TransportConnectJob
This switches TransportConnectJob to HostResolverEndpointResults. It is
currently a no-op because HostResolverEndpointResults contains the same
data as AddressList, but in a different order. But once HostResolver
starts returning data from the HTTPS DNS record (issue , and
gated by the appropriate feature flag), this CL will cause
TransportConnectJob to pick it up.

That will allow two things. First, we'll pick up additional routes
advertised in the HTTPS DNS record. Second, we can pass this data up to
SSLConnectJob (will be done in a subsequent CL) for ECH to pick up. In
principle, we can also use the ALPN information to guide
ShouldThrottleConnectForSpdy() and perhaps reduce the number of
connections made in an initial connection to the server, but this CL
does not implement that. (We'd probably need to revise the
HttpStreamFactory/TransportClientSocketPool/ConnectJob split for that.)

As part of this CL, TransportConnectJob needs ALPN information to select
usable routes. I've passed that down from the corresponding SSLConfig
when creating a ConnectJob. To make sure we do it consistently, I've
added a DCHECK and fixed the various tests to fill this in.

Bug: 1287240
Change-Id: I3b9f6a5135a59cc88f1955d0afe204f3f2ede932
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3418520
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/main@{#969665}
2022-02-10 22:23:21 +00:00
..
2021-11-08 07:38:36 +00:00
2022-02-10 09:57:50 +00:00
2022-01-19 18:19:01 +00:00
2022-02-03 14:49:22 +00:00
2022-01-11 16:47:52 +00:00
2022-01-08 04:40:57 +00:00
2022-02-08 20:13:44 +00:00

Chrome Networking Stack

This directory contains the code behind Chrome's networking stack. It is documented here.