Repository navigation
tls: secureConnect event will not be emitted if TLSSocket is created via constructor instead of tls.connect #10555
Description
Activity
Confirmed. I will document.
PTAL at #10846
@sam-github Should this issue remain open?
Yes, our documentation is incorrect, and parts of the TLS API are unuseable now (at least, not useable with documented methods and events). I tried to fix, but #10846 was rejected.
Reacted by Alex Fernández and Jonathan WilburPing @sam-github ... would you be interested in taking another run at #10846?
- added a commit that references this issue
on Dec 31, 2020 - added a commit that references this issue
on Apr 28, 2021 - added a commit that references this issue
on May 3, 2021 I wonder why on Earth this underwater stone exists. IMHO it only increases WTF-per-minute value.
- added a commit that references this issue
on May 22, 2026
In current TLS doc, secureConnect is documented as an event of TLSSocket. However, the event will only be emitted if the socket is created via tls.connect. Basically there is no sensible event to listen on for the 'connect' event if the socket is created directly via new tls.TLSSocket.