-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
x/net/http2: Required ciphers error message is confusing #34776
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
Change https://golang.org/cl/200317 mentions this issue: |
Change https://golang.org/cl/209077 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Nov 27, 2019
Updates bundled http2 to x/net git rev ef20fe5d7 for: http2: make Transport.IdleConnTimeout consider wall (not monotonic) time https://golang.org/cl/208798 (#29308) http2: make CipherSuites validation error more verbose https://golang.org/cl/200317 (#34776) http2: track unread bytes when the pipe is broken https://golang.org/cl/187377 (#28634) http2: split cookie pair into separate hpack header fields https://golang.org/cl/155657 (#29386) Fixes #29308 Fixes #28634 Change-Id: I71a03ca62ccb5ff35a5cfadd8dc705a4491ae7ea Reviewed-on: https://go-review.googlesource.com/c/go/+/209077 Reviewed-by: Ian Lance Taylor <iant@golang.org>
dteh
pushed a commit
to dteh/fhttp
that referenced
this issue
Jun 22, 2022
Fixes golang/go#34776 Change-Id: Ib76e687780781d9cc59346f722d0ea4ec033ce77 Reviewed-on: https://go-review.googlesource.com/c/net/+/200317 Reviewed-by: Bryan C. Mills <bcmills@google.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
In cipher customization code, included
TLS_AES_128_GCM_SHA256
inCipherSuites
member to atls.Config
struct, which was subsequently passed tohttp.Server
andListenAndServeTLS()
What did you expect to see?
Proper startup
What did you see instead?
http2: TLSConfig.CipherSuites is missing an HTTP/2-required AES_128_GCM_SHA256 cipher.
What the test actually wants is
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
. I imagine that prior to the introduction ofTLS_AES_128_GCM_SHA256
this error message was less ambiguous. However, it is now misleading.The text was updated successfully, but these errors were encountered: