-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Upgrade okhttp to 4.10.0 #16774
Upgrade okhttp to 4.10.0 #16774
Conversation
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.
The update itself looks good to me however I'll defer the merge to @electrum on this.
CI hit: #16653 |
Thanks for this change. I have been using OkHttp 4.10.0 in production with Trino for a while.
|
@sajjoseph does it work? :) |
Matter of fact I added HTTP/2 support in our version of Trino (I am contributing that change to airlift shortly) and OkHttp module automatically switched to HTTP/2 to communicate with Coordinator. I haven't seen any issues in our test environment. We will be promoting it to prod in a week and so we will see how older and newer clients (JDBC, CLI etc with different OkHttp versions) are behaving. |
That's great news @sajjoseph |
1b9daff
to
8c00081
Compare
Ping @electrum |
client/trino-client/src/main/java/okhttp3/internal/tls/LegacyHostnameVerifier.java
Show resolved
Hide resolved
8c00081
to
f9fa9f7
Compare
They were removed in OkHttp 4.x and we still rely on the legacy SSL hostname verification
f9fa9f7
to
1369b84
Compare
Merged, thanks! |
Release notes are not needed.