Skip to content

feat: support COMPATIBLE_TLS connectionSpec in OkHttpHttpSender#8594

Open
singhlovepreet9 wants to merge 1 commit into
open-telemetry:mainfrom
singhlovepreet9:feat/okhttp-compatible-tls
Open

feat: support COMPATIBLE_TLS connectionSpec in OkHttpHttpSender#8594
singhlovepreet9 wants to merge 1 commit into
open-telemetry:mainfrom
singhlovepreet9:feat/okhttp-compatible-tls

Conversation

@singhlovepreet9

Copy link
Copy Markdown

Fixes #7573.

This PR adds ConnectionSpec.COMPATIBLE_TLS to the OkHttpClient.Builder's connectionSpecs for HTTPS endpoints, enabling support for legacy systems like WebSphere 8.x / IBM J9 Java 1.8 that cannot satisfy the requirements of MODERN_TLS.

By configuring OkHttpHttpSender to fall back to COMPATIBLE_TLS when MODERN_TLS is unavailable, we maintain the highest possible level of security while unblocking telemetry exports on older JVMs.

@singhlovepreet9
singhlovepreet9 requested a review from a team as a code owner July 12, 2026 18:28
@linux-foundation-easycla

Copy link
Copy Markdown

CLA Not Signed

@jack-berg

Copy link
Copy Markdown
Member

Hey I gave this issue some thought and shared my analysis here: #7573 (comment)

I think we should go in a different direction with this: #8610, which embodies option d in the comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OkHttpHttpSender should support COMPATIBLE_TLS connectionSpec

2 participants