-
Notifications
You must be signed in to change notification settings - Fork 87
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
Handle TCP reset during handshake #251
Conversation
Sending the TLS alert to the peer may fail and should not replace and hide the original exception we're trying to wrap. Fixes #250.
Is this PR trying to fix #250? |
Yes, this allows the HandshakeFailed exception to be returned instead of a second exception coming from sendPacket. |
@ocheron Thank you. |
@kazu-yamamoto, @ocheron, well, it passed the first case with empty message, so I'm already satisfied :) I'm currently preparing more tests for my project and give you a report if will find something else. Thanks. |
@boris-stepanov Thank you, I guess empty message means @kazu-yamamoto To put things in context: when working on previous issues I noticed sendPacket had its own catch in |
@ocheron Would you like to merge this by yourself? Or shall I? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Handle TCP reset during handshake
Merged, thanks for reviewing. |
Here catching only IOException looks preferable as the goal is simply to ignore.