Change Default SSL Configuration #128
Open
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
The default SSL configuration has problems negotiating the TLS bits on some sites. Setting TLSv1 as the only protocol choice, got alot more (at least the set I cared about) to work.
Contributor
|
Maybe a new test case would be in order? |
|
Do you guys mind closing this one ? It looks like it has been merged manually. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The default SSL configuration has problems negotiating the TLS bits on some sites. Setting TLSv1 as the only protocol choice, got alot more (at least the set I cared about) to work.
After a bit more investigation, I think the specific sets of MS IIS servers I'm hitting have cipher/protocol specs that are incompatible with the otherside. Anyways, no SSLv3 solves my problem, which for now is scraping some websites.