Skip to content
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 no longer uses default ssl context. #518

Merged
merged 1 commit into from
Feb 9, 2014

Conversation

codefromthecrypt
Copy link

closes #184

@@ -202,8 +204,7 @@ public OkResponseCache getOkResponseCache() {
/**
* Sets the socket factory used to secure HTTPS connections.
*
* <p>If unset, the {@link HttpsURLConnection#getDefaultSSLSocketFactory()
* system-wide default} SSL socket factory will be used.
* <p>If unset, a lazy created SSL socket factory will be used.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: lazily-created

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@codefromthecrypt
Copy link
Author

PTAL

@swankjesse
Copy link
Member

LGTM

Test to check sure multiple copies created with copyWithDefaults() get the same SSLSocketFactory? Seems like the sort of behavior that could bitrot away without a test.

swankjesse added a commit that referenced this pull request Feb 9, 2014
@swankjesse swankjesse merged commit f11832d into master Feb 9, 2014
@codefromthecrypt
Copy link
Author

Will do.

@JakeWharton JakeWharton deleted the adrian.okclient-provided-sslcontext branch April 17, 2014 21:50
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.

OkHttp changes the global SSL context, breaks other HTTP clients
2 participants