crypto/tls: client gets nondescriptive EOF error if server stops connection after client hello #44663
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?
Made HTTPS request against a bad server that was terminating connections upon seeing TLS client hello.
Click to expand sample bad server
What did you expect to see?
Expected to see some contextual information on the error indicating issue with tls or better yet tls handshake. For comparision,
curl
, in this case, emittscurl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL
Most errors from the
crypto/tls
package prefix their errors with additional context in the form oftls: {extra info} ...
in a helpful way, but thisEOF
error here appears to be an exception.What did you see instead?
Got a nondescriptive
EOF
error.edit: reformat markdown codeblock
The text was updated successfully, but these errors were encountered: