[3.11] GH-113214: Fix SSLProto exception handling in SSL-over-SSL scenarios (GH-113334) #113340
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 wrapped,
_SSLProtocolTransport._force_close(exc)
is called just like in the unwrapped scenario_SelectorTransport._force_close(exc)
or_ProactorBasePipeTransport._force_close(exc)
would be called, except here the exception needs to be passed through theSSLProtocol._abort()
method, which didn't accept an exception object.This commit ensures that this path works, in the same way that the uvloop implementation of SSLProto passes on the exception (on which the current implementation of SSLProto is based).
(cherry picked from commit 1ff0238)
Co-authored-by: Martijn Pieters [email protected]