Support ConnectionSpec on Okhttp client and support null ConnectionSpec parameters#12677
Draft
megla-tlanghorst wants to merge 4 commits intogrpc:masterfrom
Draft
Support ConnectionSpec on Okhttp client and support null ConnectionSpec parameters#12677megla-tlanghorst wants to merge 4 commits intogrpc:masterfrom
megla-tlanghorst wants to merge 4 commits intogrpc:masterfrom
Conversation
|
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
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.
I'm deploying a pretty customized gRPC client/server system which uses highly customized
SSLSocketFactorys on both sides. Currently though it is not possible to customize theConnectionSpecwhen supplyingSslSocketFactoryChannelCredentialsas the security parameters get frozen. This results in me having to use it like this:And on the server side I needed to rebuild my own
ConnectionSpecclass if I didn't want to have a really old okhttp dependency just for that class. The new overloads just take the raw parameters, liketlsConnectionSpecso you don't need to copy it from some other class.With this PR it's now possible to do like this:
Allowing the following:
ConnectionSpecparameters to theSslSocketFactoryChannelCredentialstlsConnectionSpec, so you don't need a dependency on okhttp (or reimplementation), just for theConnectionSpecclassnullfortlsVersionandcipherSuiteList, so you can set them to "don't touch my socket", like it's possible in okhttp itself and already intended in some of this code