-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(client): allow both IPv6 and IPv4 local addresses #2172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
10408ea
to
71b8045
Compare
gitcop is not happy with the commit message for some reason. Though, I've tried to follow the guidelines. Can someone clarify what's wrong with it please? |
c3976b3
to
fe6b9dd
Compare
@seanmonstar Sorry for poking you, but may ask your feedback on the PR? |
d92c485
to
a5e94ac
Compare
hopeless bump |
@seanmonstar Sorry for the ping again, your feedback will be appreciated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about losing the notifications on this. I'm fine with add the ability to do this, we just need to prevent breaking changes :)
@seanmonstar addressed the comments |
Currently HttpConnector::set_local_address method accepts a single argument. Server might not support IPv6 or IPv4. Therefore, the only solution at the moment is to manually perform DNS resolution and pick appropriate local address family. This is inefficient, as leads to 2 DNS lookups per request. This commit allows specifying both IPv4 and IPv6, so connector can decide which one to use based on DNS resolution results.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
…v6 and IPv4 local addrs (hyperium#2172) Currently HttpConnector::set_local_address method accepts a single argument. Server might not support IPv6 or IPv4. Therefore, the only solution at the moment is to manually perform DNS resolution and pick appropriate local address family. This is inefficient, as leads to 2 DNS lookups per request. This commit allows specifying both IPv4 and IPv6, so connector can decide which one to use based on DNS resolution results.
Closes: #2169