Fix spurious "success" on SSL system errors: #182
Closed
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
Fix boostorg/beast#807 Fix boostorg/beast#1373 This resolves an issue where an ssl::stream read operation returns a successful error code but zero bytes transferred, violating its contract. * Treat SSL_ERROR_ZERO_RETURN as EOF * Use the ssl category for sys_error * On error, if sys_error is 0 (success), return ssl::errors::read_sys_error instead.
|
Fixed here; ce7e3bb |
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.
Fix boostorg/beast#807
Fix boostorg/beast#1373
This resolves an issue where an ssl::stream read operation
returns a successful error code but zero bytes transferred,
violating its contract.
Treat SSL_ERROR_ZERO_RETURN as EOF
Use the ssl category for sys_error
On error, if sys_error is 0 (success),
return ssl::errors::read_sys_error instead.