-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
Closed
Labels
caresIssues and PRs related to the c-ares dependency or the cares_wrap binding.Issues and PRs related to the c-ares dependency or the cares_wrap binding.dnsIssues and PRs related to the dns subsystem.Issues and PRs related to the dns subsystem.feature requestIssues that request new features to be added to Node.js.Issues that request new features to be added to Node.js.httpsIssues or PRs related to the https subsystem.Issues or PRs related to the https subsystem.tlsIssues and PRs related to the tls subsystem.Issues and PRs related to the tls subsystem.
Description
Is your feature request related to a problem? Please describe.
I'd like to make an HTTPS request to a server that uses a self-signed certificate that follows the DANE protocol (Wikipedia)
Describe the solution you'd like
I believe the best option would be an extra option on HTTPS request:
https.get('https://example.com', {dane: true})
Describe alternatives you've considered
I tried to create a new https.Agent
that forces rejectUnauthorized: false
;
Then, I got the tlsSocket
instance in the keylog
event and added a listener for the secureConnect
event;
This moment I realised that the DNS api don't have a resolveTLSA
.
Not sure how to continue from here.
awwright and abwesend890
Metadata
Metadata
Assignees
Labels
caresIssues and PRs related to the c-ares dependency or the cares_wrap binding.Issues and PRs related to the c-ares dependency or the cares_wrap binding.dnsIssues and PRs related to the dns subsystem.Issues and PRs related to the dns subsystem.feature requestIssues that request new features to be added to Node.js.Issues that request new features to be added to Node.js.httpsIssues or PRs related to the https subsystem.Issues or PRs related to the https subsystem.tlsIssues and PRs related to the tls subsystem.Issues and PRs related to the tls subsystem.
Type
Projects
Status
Awaiting Triage