TLS setup harmonization in the classic and async connection operators #540
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
|
@arturobernalg Please take a look. |
ok2c
force-pushed
the
tls_setup_harmonization
branch
from
d6f50a6
to
0d6e57a
Compare
…d their plain and SSL implementations in favor of DefaultClientTlsStrategy
ok2c
force-pushed
the
tls_setup_harmonization
branch
from
0d6e57a
to
fd2961a
Compare
|
If I hear no objections I will merge this PR in the coming days. |
|
@ok2c Causes HTTPCLIENT-2348. |
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.
ConnectionSocketFactory/LayeredConnectionSocketFactoryAPIs in favor ofTlsSocketStrategyconsistent withTlsStrategyused by the async APIs.PlainConnectionSocketFactorywithout a direct replacement.SSLConnectionSocketFactoryin favor ofDefaultClientTlsStrategythat can be used with classic and async transports