-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
okhttp: introduced new TLS1.2 cipher suites and internal okhttp implementation for TLS1.3 prepared. #8650
Conversation
We can't review until you agree to the CLA. If you have trouble, just tell us. |
I agreed the CLA, but it seems that I used the wrong username for my initial commit. Is there a way to change this? or shall I close the PR and create a new one with the commits issued with the correct username? |
@beatrausch, you can do whatever rewriting of the commits you need (e.g., via rebase) and then just force-push to your fork's branch. This PR will track that branch, and then notice the new authorship. |
Additional TLS1.2 cipher suites added Default connection spec synced with netty Introduced new method for internal connection in OkHttpChannelBuilder
daf3c20
to
cdb8dc5
Compare
@beatrausch Can you please drop unrelated commits? |
cdb8dc5
to
b861c5e
Compare
Sorry, I dropped the commits |
@beatrausch, thank you! |
The PR introduces new TLS 1.2 cipher suites (#8610) and prepares the internal okhttp implementation for TLS1.3. A new method for using a internal ConnectionSpec was added to be able to use the newly introduced cipher suites in the OkHttpChannelBuilder. Okhttp cipher suites synchronized with the ones form netty.