Skip to content

Conversation

seanmonstar
Copy link
Member

The DNS resolver part of HttpConnector used to require resolving to
IpAddrs, and this changes it so that they resolve to SocketAddrs.
The main benefit here is allowing for resolvers to set the IPv6 zone ID
when resolving, but it also just more closely matches
std::net::ToSocketAddrs.

Closes #1937

BREAKING CHANGE: Custom resolvers used with HttpConnector must change
to resolving to an iterator of SocketAddrs instead of IpAddrs.

The DNS resolver part of `HttpConnector` used to require resolving to
`IpAddr`s, and this changes it so that they resolve to `SocketAddr`s.
The main benefit here is allowing for resolvers to set the IPv6 zone ID
when resolving, but it also just more closely matches
`std::net::ToSocketAddrs`.

Closes #1937

BREAKING CHANGE: Custom resolvers used with `HttpConnector` must change
  to resolving to an iterator of `SocketAddr`s instead of `IpAddr`s.
@seanmonstar seanmonstar merged commit b4e2433 into master Dec 3, 2020
@seanmonstar seanmonstar deleted the resolve-to-socket-addrs branch December 3, 2020 22:21
BenxiangGe pushed a commit to BenxiangGe/hyper that referenced this pull request Jul 26, 2021
…#2346)

The DNS resolver part of `HttpConnector` used to require resolving to
`IpAddr`s, and this changes it so that they resolve to `SocketAddr`s.
The main benefit here is allowing for resolvers to set the IPv6 zone ID
when resolving, but it also just more closely matches
`std::net::ToSocketAddrs`.

Closes hyperium#1937

BREAKING CHANGE: Custom resolvers used with `HttpConnector` must change
  to resolving to an iterator of `SocketAddr`s instead of `IpAddr`s.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant