feat: support COMPATIBLE_TLS connectionSpec in OkHttpHttpSender#8594
feat: support COMPATIBLE_TLS connectionSpec in OkHttpHttpSender#8594singhlovepreet9 wants to merge 3 commits into
Conversation
|
|
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. |
Pull request dashboard statusStatus last refreshed: 2026-07-20 21:22:53 UTC.
This automated status or its linked feedback items may be incorrect. If something looks wrong, report it with the result you expected. |
253ebda to
1439a69
Compare
|
1439a69 to
515d117
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #8594 +/- ##
=========================================
Coverage 91.64% 91.64%
- Complexity 10348 10372 +24
=========================================
Files 1013 1013
Lines 27380 27441 +61
Branches 3218 3230 +12
=========================================
+ Hits 25092 25149 +57
- Misses 1558 1559 +1
- Partials 730 733 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Fixes #7573.
This PR adds
ConnectionSpec.COMPATIBLE_TLSto theOkHttpClient.Builder'sconnectionSpecsfor HTTPS endpoints, enabling support for legacy systems like WebSphere 8.x / IBM J9 Java 1.8 that cannot satisfy the requirements ofMODERN_TLS.By configuring
OkHttpHttpSenderto fall back toCOMPATIBLE_TLSwhenMODERN_TLSis unavailable, we maintain the highest possible level of security while unblocking telemetry exports on older JVMs.