From f66d99ae5339f930f7ae109046464d018a270bc1 Mon Sep 17 00:00:00 2001 From: Tim Gerk Date: Sun, 15 Jan 2023 17:42:34 -0800 Subject: [PATCH] doc: add note to tls docs about secureContext availability tls.createServer() and new tls.Server() ignore secureContext option. --- doc/api/tls.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/api/tls.md b/doc/api/tls.md index 8db7ac2f193291..32e0d5b5371489 100644 --- a/doc/api/tls.md +++ b/doc/api/tls.md @@ -1940,8 +1940,9 @@ from `process.argv` as the default value of the `sessionIdContext` option, other APIs that create secure contexts have no default value. The `tls.createSecureContext()` method creates a `SecureContext` object. It is -usable as an argument to several `tls` APIs, such as [`tls.createServer()`][] -and [`server.addContext()`][], but has no public methods. +usable as an argument to several `tls` APIs, such as [`server.addContext()`][], +but has no public methods. The [`tls.Server`][] constructor and the +[`tls.createServer()`][] method do not support the `secureContext` option. A key is _required_ for ciphers that use certificates. Either `key` or `pfx` can be used to provide it.