You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.9.1 windows/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
windows amd64
What did you do?
I am looking for tls server name indication routing and found.
There are different github repositories about that.
They all need to parse tls hello message to get the SNI.
I do think that using "crypto/tls" is the best.
Just to have a single reference on what is tls for golang.
In the end such projects need to implement their own code to decode hello message because most of "crypto/tls" constants and unmarshaling methods are not exported.
What did you expect to see?
Basic constants exported for common tls.
Unmarshaling methods exported for tls "headers"
What did you see instead?
All these informations are not exported by "crypto/tls"
The text was updated successfully, but these errors were encountered:
odeke-em
changed the title
Open crypto/tls a bit.
crypto/tls: export some constants and helpers such as Unmarshaling methods for headers
Feb 3, 2018
Sorry, we don't want to export more stuff from the crypto/tls package. Any extra API is extra godoc and is extra user confusion when trying to read the docs.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.9.1 windows/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?windows amd64
What did you do?
I am looking for tls server name indication routing and found.
There are different github repositories about that.
They all need to parse tls hello message to get the SNI.
I do think that using "crypto/tls" is the best.
Just to have a single reference on what is tls for golang.
In the end such projects need to implement their own code to decode hello message because most of "crypto/tls" constants and unmarshaling methods are not exported.
What did you expect to see?
Basic constants exported for common tls.
Unmarshaling methods exported for tls "headers"
What did you see instead?
All these informations are not exported by "crypto/tls"
The text was updated successfully, but these errors were encountered: