diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2008-08-27 08:01:59 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2008-08-27 08:01:59 +0000 |
| commit | 6f53cf9cc6960a38c586cf0c36642486caf02b92 (patch) | |
| tree | e8a5f027d9aa488529a30fb633c0bff2361c22b3 | |
| parent | 1056202b48255c39e08a1af815cac44f3be5fa09 (diff) | |
s/you you/you/ thanks to hexo6 at wp.pl
| -rw-r--r-- | docs/TheArtOfHttpScripting | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/TheArtOfHttpScripting b/docs/TheArtOfHttpScripting index 3d237b489..e4212db71 100644 --- a/docs/TheArtOfHttpScripting +++ b/docs/TheArtOfHttpScripting @@ -375,12 +375,11 @@ Date: May 28, 2008 11.1 Certificates In the HTTPS world, you use certificates to validate that you are the one - you you claim to be, as an addition to normal passwords. Curl supports - client-side certificates. All certificates are locked with a pass phrase, - which you need to enter before the certificate can be used by curl. The pass - phrase can be specified on the command line or if not, entered interactively - when curl queries for it. Use a certificate with curl on a HTTPS server - like: + you claim to be, as an addition to normal passwords. Curl supports client- + side certificates. All certificates are locked with a pass phrase, which you + need to enter before the certificate can be used by curl. The pass phrase + can be specified on the command line or if not, entered interactively when + curl queries for it. Use a certificate with curl on a HTTPS server like: curl -E mycert.pem https://that.secure.server.com |