crypto/tls: Conn missing CloseRead / CloseWrite

[gopherbot]

by justin@fathomdb.com:

CloseRead / CloseWrite functions are missing from tls.Conn.

Yet, this is the recommended way to proxy between TCP connections:
http://grokbase.com/t/gg/golang-nuts/131k81bse0/go-nuts-use-of-closed-network-connection-error-from-tcpconn-read

They should probably be defined on net.Conn

[bradfitz]

Comment 1:

Labels changed: added repo-main.

Owner changed to @agl.

Status changed to Accepted.

[mikioh]

Comment 2:

> They should probably be defined on net.Conn
unfortunately we can't break the go1 contract; http://golang.org/doc/go1compat/.

[rsc]

I don't think this will happen. The input to TLS is a net.Conn, and we can't add them there. crypto/tls would have to sniff for them, and what if the underlying net.Conn doesn't support them?

[cpuguy83]

@rsc It may be helpful here to be able to get the underlying net.Conn?
We currently have our own copy of tls.Dial which we use to store the underlying conn and provide our own CloseWrite method.

[gopherbot]

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

[gopherbot]

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

[mikioh]

Reopening, CL 25159 has been reverted.