tls.connect({checkServerIdentity}) option cannot be a null - must be … #1638
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
charmander
approved these changes
May 5, 2018
|
the error: |
|
The issue is easy to test, so the fix should include a test where we pass in |
|
@vitaly-t Tests and CI aren’t set up for SSL. Working on it. |
|
oops sorry about that - pushing new patch version now |
|
published fix at |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
…a method or not exist.
Defaults to built-in
tls.checkServerIdentitymethod in the event one is not passed intopgConfig.sslFound breaking in v7.4.2 vs v7.4.1 a la 4905471
cc @tobio @brianc