Skip to content
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

net/http: set Dialer.DualStack on DefaultTransport? #15324

Closed
bradfitz opened this issue Apr 15, 2016 · 4 comments
Closed

net/http: set Dialer.DualStack on DefaultTransport? #15324

bradfitz opened this issue Apr 15, 2016 · 4 comments

Comments

@bradfitz
Copy link
Contributor

The http package doesn't set net.Dialer.DualStack on its default transport configuration. Maybe it should.

@mikioh, @pmarks-net, thoughts?

(This might've helped @jfrazelle who I recall was fighting IPv6 once)

@bradfitz bradfitz self-assigned this Apr 15, 2016
@bradfitz bradfitz added this to the Go1.7 milestone Apr 15, 2016
@pmarks-net
Copy link
Contributor

Happy Eyeballs is a prisoner's dilemma: if one client uses it, it gains an advantage over its neighbors when the network is broken. But if everyone uses it, then everyone pays the 300ms penalty, and the network never gets fixed.

I have no strong opinion on whether or not it should be the default.

@bradfitz
Copy link
Contributor Author

bradfitz commented Apr 16, 2016

@pmarks-net, maybe we spew a log message to stderr whenever the slow dial in happy eyeballs win the race. "WARNING: your IPv6 is broken; fell back slowly to IPv4" :-)

@mikioh
Copy link
Contributor

mikioh commented Apr 19, 2016

I'd like to hear the detail of the fight. It might be a help to understand what would be a root cause of bad, ambient unaware selection on multiple IP links, addresses, various name to address mappings.

@bradfitz bradfitz modified the milestones: Go1.8Maybe, Go1.7, Go1.8Early May 10, 2016
@gopherbot
Copy link

CL https://golang.org/cl/28077 mentions this issue.

@golang golang locked and limited conversation to collaborators Aug 31, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants