GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: clarify `tls.Server` `'connection'` event documentation · nodejs/node@4883904

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • doc/api
    • tls.md
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎doc/api/tls.md‎

Copy file name to clipboardExpand all lines: doc/api/tls.md
+3-2Lines changed: 3 additions & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -480,8 +480,9 @@ added: v0.3.2
480480
* `socket` {stream.Duplex}
481481

482482
This event is emitted when a new TCP stream is established, before the TLS
483-
handshake begins. `socket` is typically an object of type [`net.Socket`][].
484-
Usually users will not want to access this event.
483+
handshake begins. `socket` is typically an object of type [`net.Socket`][] but
484+
will not receive events unlike the socket created from the [`net.Server`][]
485+
`'connection'` event. Usually users will not want to access this event.
485486

486487
This event can also be explicitly emitted by users to inject connections
487488
into the TLS server. In that case, any [`Duplex`][] stream can be passed.

0 commit comments

Comments
0 (0)
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.