mirror of
https://github.com/curl/curl.git
synced 2026-08-06 06:06:15 +03:00
620401f193
After Gmail called out the typo I fixed on
532d89a866, I've decided to paste the
whole man page into Google docs and check what other issues it would
spot.
I know, it sounds silly, but I've just spent the last hour and a half
going over each one of them and fixing everything which was a true
finding and non-controversial.
Closes #17480
29 lines
877 B
Markdown
29 lines
877 B
Markdown
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: capath
|
|
Arg: <dir>
|
|
Help: CA directory to verify peer against
|
|
Protocols: TLS
|
|
Category: tls
|
|
Added: 7.9.8
|
|
Multi: single
|
|
See-also:
|
|
- cacert
|
|
- dump-ca-embed
|
|
- insecure
|
|
Example:
|
|
- --capath /local/directory $URL
|
|
---
|
|
|
|
# `--capath`
|
|
|
|
Use the specified certificate directory to verify the peer. Multiple paths can
|
|
be provided by separating them with colon (`:`) (e.g. `path1:path2:path3`). The
|
|
certificates must be in PEM format, and if curl is built against OpenSSL, the
|
|
directory must have been processed using the c_rehash utility supplied with
|
|
OpenSSL. Using --capath can allow OpenSSL-powered curl to make SSL-connections
|
|
much more efficiently than using --cacert if the --cacert file contains many
|
|
CA certificates.
|
|
|
|
If this option is set, the default capath value is ignored.
|