Draft: Add TLS protocol configuration for OTLP HTTP exporters#8638
Closed
ZapolyarnyDev wants to merge 1 commit into
Closed
Draft: Add TLS protocol configuration for OTLP HTTP exporters#8638ZapolyarnyDev wants to merge 1 commit into
ZapolyarnyDev wants to merge 1 commit into
Conversation
|
|
Author
|
Closing as a duplicate of #8610. I opened this draft before noticing the existing implementation. Thanks! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Relates to #7573
Summary
This draft adds
setEnabledProtocols(List<String>)to OTLP HTTP exporter builders.The configured protocols are passed to HTTP senders:
ConnectionSpec.SSLParametersWhen unset, existing TLS behavior remains unchanged
Motivation
Some environments require enabling TLS protocols that are not part of OkHttp's default
MODERN_TLSconfiguration. This provides an explicit opt-in without changing defaults.Security
No legacy protocols are enabled by default. Users must explicitly configure the protocols they want to allow.
Open questions
This draft currently covers HTTP senders only. Feedback is welcome on: