-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
tls: introduce secureContext
for tls.connect
#8959
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
tls: introduce secureContext
for tls.connect
#8959
Conversation
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.
LGTM
6a126fb
to
004d665
Compare
@thealphanerd should it be landed? |
Looks like this needs to be rebased. |
Add `secureContext` option to `tls.connect`. It is useful for caching client certificates, key, and CA certificates. PR-URL: nodejs#4246 Reviewed-By: James M Snell <jasnell@gmail.com>
22d7fc6
to
125977b
Compare
@jasnell Voila! Though, there were no conflict 😉 This PR will become stale again unless we'll land it. cc @thealphanerd |
I'm good for this to land. |
@thealphanerd should I just land it? How does it work? |
you can land it on staging 😊 |
Landed in d9b5437, thank you! |
Checklist
make -j8 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
tls
Description of change
Add
secureContext
option totls.connect
. It is useful for cachingclient certificates, key, and CA certificates.
PR-URL: #4246
Reviewed-By: James M Snell jasnell@gmail.com
Backport of: #4246 (comment)