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: (&Dialer{DualStack: true}).DIal w/ "tcp" returns a nested error #6795

Closed
mikioh opened this issue Nov 20, 2013 · 5 comments

Comments

Projects
None yet
3 participants
@mikioh
Copy link
Contributor

commented Nov 20, 2013

What steps will reproduce the problem?
1. Call  (&Dialer{DualStack: true}.DIal("tcp", "dead server's
FQDN")
2.
3.

What is the expected output? What do you see instead?
dial tcp <address:port literal>: connection refused

Please use labels and text to provide additional information.
go1.2rc5
Dial failed: dial tcp <address:port literal>: dial tcp <address:port
literal>: connection refused

dialMulti certainly returns a nested error.
@rsc

This comment has been minimized.

Copy link
Contributor

commented Nov 27, 2013

Comment 2:

Labels changed: added go1.3maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 3:

Labels changed: added release-none, removed go1.3maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 4:

Labels changed: added repo-main.

@mikioh

This comment has been minimized.

Copy link
Contributor Author

commented Dec 5, 2013

@mikioh

This comment has been minimized.

Copy link
Contributor Author

commented Dec 19, 2013

Comment 6:

This issue was closed by revision 7eb45d3.

Status changed to Fixed.

@mikioh mikioh added fixed labels Dec 19, 2013

@golang golang locked and limited conversation to collaborators Jun 25, 2016

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.