-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ApacheHttpClientChannels no longer complains about Unsupported ciphersuite
#415
Conversation
Generate changelog in
|
…_CHACHA20_POLY1305_SHA256
485a6e9
to
a7af40e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, thanks Dan!
} | ||
} | ||
|
||
log.info( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we check !unsupported.isEmpty()
?
Out of curiosity, do you know why this wasn't caught in the existing |
I don't think this repo actually uses TLS anywhere |
Released 0.9.2 |
Before this PR
In my witchcraft PR, I'm unable to make calls using ApacheHttpClientChannels due to:
After this PR
==COMMIT_MSG==
ApacheHttpClientChannels no longer complains about
Unsupported ciphersuite
==COMMIT_MSG==
Possible downsides?