You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different sections said different things about what the `ca` argument
should look like. This commit harmonizes them.
Ref: #4099
PR-URL: #4213
Reviewed-By: Roman Reiss <[email protected]>
Copy file name to clipboardExpand all lines: doc/api/https.markdown
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,8 +164,9 @@ The following options from [`tls.connect()`][] can also be specified. However, a
164
164
-`key`: Private key to use for SSL. Default `null`.
165
165
-`passphrase`: A string of passphrase for the private key or pfx. Default `null`.
166
166
-`cert`: Public x509 certificate to use. Default `null`.
167
-
-`ca`: An authority certificate or array of authority certificates to check
168
-
the remote host against.
167
+
-`ca`: A string, `Buffer` or array of strings or `Buffer`s of trusted
168
+
certificates in PEM format. If this is omitted several well known "root"
169
+
CAs will be used, like VeriSign. These are used to authorize connections.
169
170
-`ciphers`: A string describing the ciphers to use or exclude. Consult
170
171
<http://www.openssl.org/docs/apps/ciphers.html#CIPHER_LIST_FORMAT> for
0 commit comments