fix TLS infinite loop when peer close the connection unexpectedly #168
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.
OpenSSL's
SSL_read/SSL_writedoes not seem to handle zero return from the underlying BIO correctly. It keeps reportingSSL_WANT_READin this case, instead ofSSL_ZERO_RETURNor others. So if the peer closed the underlying connection unexpectedly when@tls.Tlsis attempting a read (e.g. inconnectorread), current implementation falls into infinite loop. This PR fixes the issue and handle peer connection close properly.