Don't report non ssl related errors during ssl handshake as fatal in default socket provider #6436
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.
What, How & Why?
Starting with the changes made to integrate Platform Networking, the handle ssl handshake was converting any connection or communication failure during ssl certificate negotiation as a "tls handshake failed" fatal error. These changes update the handling of these errors to report a "tls handshake failed" only when the ssl certificate is rejected and uses the "connection failed" non-fatal error for non-tls handshake errors.
Fixes #6434
☑️ ToDos
[ ] 🚦 Tests (or not relevant)[ ] C-API, if public C++ API changed.