From: Daniel Stenberg Date: Wed, 27 Aug 2008 08:01:59 +0000 (+0000) Subject: s/you you/you/ thanks to hexo6 at wp.pl X-Git-Tag: upstream/7.37.1~7308 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6f53cf9cc6960a38c586cf0c36642486caf02b92;p=platform%2Fupstream%2Fcurl.git s/you you/you/ thanks to hexo6 at wp.pl --- diff --git a/docs/TheArtOfHttpScripting b/docs/TheArtOfHttpScripting index 3d237b4..e4212db 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