doc: document 'ciphers' option of tls.connect
This option has been there for a long time, but has never been documented. It's functionally identical to the server counterpart. PR-URL: https://github.com/iojs/io.js/pull/845 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
This commit is contained in:
parent
b5f25a963c
commit
ed240f44f7
@ -301,6 +301,9 @@ Creates a new client connection to the given `port` and `host` (old API) or
|
|||||||
format. If this is omitted several well known "root" CAs will be used,
|
format. If this is omitted several well known "root" CAs will be used,
|
||||||
like VeriSign. These are used to authorize connections.
|
like VeriSign. These are used to authorize connections.
|
||||||
|
|
||||||
|
- `ciphers`: A string describing the ciphers to use or exclude, separated by
|
||||||
|
`:`. Uses the same default cipher suite as `tls.createServer`.
|
||||||
|
|
||||||
- `rejectUnauthorized`: If `true`, the server certificate is verified against
|
- `rejectUnauthorized`: If `true`, the server certificate is verified against
|
||||||
the list of supplied CAs. An `'error'` event is emitted if verification
|
the list of supplied CAs. An `'error'` event is emitted if verification
|
||||||
fails; `err.code` contains the OpenSSL error code. Default: `true`.
|
fails; `err.code` contains the OpenSSL error code. Default: `true`.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user