Allow setting timeout during TLS Handshake #80
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please consider this PR, it will be appreciated by anyone looking to use the TLS functionality. |
Buggy clients might never respond during the TLS handshake phase. This change adds a config setting to set a read timeout before calling handshake. I think the handshake involves multiple reads but this setting should help with clients who never respond.
munkyboy
force-pushed
the
handshake-timeout
branch
from
e4c383a
to
8c4bbc0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Buggy clients might never respond during the TLS handshake phase. This
change adds a config setting to set a read timeout before calling
handshake. I think the handshake involves multiple reads but this
setting should help with clients who never respond.