Navigation Menu

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

Jump to bottom

crypto/tls: Conn.Close returns non-nil error #1037

Closed
adg opened this issue Aug 22, 2010 · 2 comments
Closed

crypto/tls: Conn.Close returns non-nil error #1037

adg opened this issue Aug 22, 2010 · 2 comments
Labels
FrozenDueToAge

Comments

@adg
Copy link
Contributor

adg commented Aug 22, 2010 

When closing a connection, the error "local error: close notify" is returned
on success.

This behaviour should either be documented, or the Close method should return nil for
this specific case.
@agl
Copy link
Contributor

agl commented Sep 10, 2010

Comment 1:

http://golang.org/cl/2107048/

Status changed to Started.

@agl
Copy link
Contributor

agl commented Sep 10, 2010

Comment 2:

This issue was closed by revision 5011c27.

Status changed to Fixed.

@adg adg added fixed labels Sep 10, 2010
@mikioh mikioh changed the title crypto/tls conn.Close returns non-nil error crypto/tls: Conn.Close returns non-nil error Jan 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
FiloSottile pushed a commit to FiloSottile/go that referenced this issue Oct 12, 2018
@agl
crypto/tls: don't return an error from Close()
4c5892d 
Fixes golang#1037.

R=adg, rsc1
CC=golang-dev
https://golang.org/cl/2107048
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@agl @adg @gopherbot