-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
net: fix family autoselection SSL connection handling #48189
net: fix family autoselection SSL connection handling #48189
Conversation
const { request } = require('https'); | ||
|
||
request( | ||
'https://nodejs.org/en', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this test go in test/internet/ if it's attempting to reach an internet host?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I didn't know about it. Fixed now.
const { request } = require('https'); | ||
|
||
request( | ||
'https://nodejs.org/en', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is reaching out to the internet this should go in internet
and not parallel
. It should also be using a constant from common/internet to allow people to run the test suites in places that restrict access to some addresses.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I didn't know about this. This is fixed now.
7425b2d
to
5150216
Compare
@nodejs/build I have a failure in GH suite but I don't think it's related to my changes. Can I ignore or do you first want to address it? |
Landed in 26450c5 |
PR-URL: #48189 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
The test-internet failure was confirmed to be unrelated and we opened #48262 for it. |
PR-URL: #48189 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
PR-URL: nodejs#48189 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
PR-URL: nodejs#48189 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
PR-URL: nodejs#48189 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
PR-URL: nodejs#48189 Backport-URL: Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
PR-URL: nodejs#48189 Backport-PR-URL: Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
PR-URL: nodejs#48189 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
PR-URL: #48189 Backport-PR-URL: #49183 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Marco Ippolito <[email protected]>
This PR fixes SSL connection attempts by not attempting to restore SSL information (like server name) if such informations are not available anymore.
Fixes #48000.