We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(split into #820)
Add APIs to configure HTTP engine TLS context.
This may be at the common HttpClientEngineConfig level or at individual engine config level depending on what makes sense.
HttpClientEngineConfig
Possible knobs:
Not every engine will support all of these or even if they do may make it difficult to map a common API to.
After these changes are made, coordinate updates to the Developer Guide to clarify how to configure TLS (especially min version).
The text was updated successfully, but these errors were encountered:
Resolving this issue will be a breaking change. See the BREAKING: Streamlined TLS configuration post for more details.
Sorry, something went wrong.
ianbotsf
Successfully merging a pull request may close this issue.
(split into #820)
Add APIs to configure HTTP engine TLS context.
This may be at the common
HttpClientEngineConfig
level or at individual engine config level depending on what makes sense.Possible knobs:
CA certs (trust manager)(handled in Enhanced TLS configuration #820)Cipher preferences(handled in Enhanced TLS configuration #820)Certificate pinning(handled in Enhanced TLS configuration #820)Host name verifier(handled in Enhanced TLS configuration #820)Not every engine will support all of these or even if they do may make it difficult to map a common API to.
After these changes are made, coordinate updates to the Developer Guide to clarify how to configure TLS (especially min version).
The text was updated successfully, but these errors were encountered: