Handle error when wolfSSL_write() returns 0#17
Merged
cconlon merged 1 commit intowolfSSL:masterfrom Nov 6, 2020
Merged
Conversation
tmael
force-pushed
the
write_check_ret0
branch
from
fe1f677 to
2bd4a67
Compare
tmael
force-pushed
the
write_check_ret0
branch
from
2bd4a67 to
8459254
Compare
cconlon
approved these changes
Nov 6, 2020
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When a peer unexpectedly closes or resets the connection before receiving all data, write() returns 0 and it should be handled as an error case.