Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

CURLMANUAL.rtf 34KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962
  1. LATEST VERSION
  2. You always find news about what's going on as well as the latest versions
  3. from the curl web pages, located at:
  4. http://curl.haxx.se
  5. SIMPLE USAGE
  6. Get the main page from Netscape's web-server:
  7. curl http://www.netscape.com/
  8. Get the README file the user's home directory at funet's ftp-server:
  9. curl ftp://ftp.funet.fi/README
  10. Get a web page from a server using port 8000:
  11. curl http://www.weirdserver.com:8000/
  12. Get a list of a directory of an FTP site:
  13. curl ftp://cool.haxx.se/
  14. Get the definition of curl from a dictionary:
  15. curl dict://dict.org/m:curl
  16. Fetch two documents at once:
  17. curl ftp://cool.haxx.se/ http://www.weirdserver.com:8000/
  18. Get a file off an FTPS server:
  19. curl ftps://files.are.secure.com/secrets.txt
  20. or use the more appropriate FTPS way to get the same file:
  21. curl --ftp-ssl ftp://files.are.secure.com/secrets.txt
  22. Get a file from an SSH server using SFTP:
  23. curl -u username sftp://shell.example.com/etc/issue
  24. Get a file from an SSH server using SCP using a private key to authenticate:
  25. curl -u username: --key ~/.ssh/id_dsa --pubkey ~/.ssh/id_dsa.pub \
  26. scp://shell.example.com/~/personal.txt
  27. Get the main page from an IPv6 web server:
  28. curl -g "http://[2001:1890:1112:1::20]/"
  29. DOWNLOAD TO A FILE
  30. Get a web page and store in a local file:
  31. curl -o thatpage.html http://www.netscape.com/
  32. Get a web page and store in a local file, make the local file get the name
  33. of the remote document (if no file name part is specified in the URL, this
  34. will fail):
  35. curl -O http://www.netscape.com/index.html
  36. Fetch two files and store them with their remote names:
  37. curl -O www.haxx.se/index.html -O curl.haxx.se/download.html
  38. USING PASSWORDS
  39. FTP
  40. To ftp files using name+passwd, include them in the URL like:
  41. curl ftp://name:passwd@machine.domain:port/full/path/to/file
  42. or specify them with the -u flag like
  43. curl -u name:passwd ftp://machine.domain:port/full/path/to/file
  44. FTPS
  45. It is just like for FTP, but you may also want to specify and use
  46. SSL-specific options for certificates etc.
  47. Note that using FTPS:// as prefix is the "implicit" way as described in the
  48. standards while the recommended "explicit" way is done by using FTP:// and
  49. the --ftp-ssl option.
  50. SFTP / SCP
  51. This is similar to FTP, but you can specify a private key to use instead of
  52. a password. Note that the private key may itself be protected by a password
  53. that is unrelated to the login password of the remote system. If you
  54. provide a private key file you must also provide a public key file.
  55. HTTP
  56. Curl also supports user and password in HTTP URLs, thus you can pick a file
  57. like:
  58. curl http://name:passwd@machine.domain/full/path/to/file
  59. or specify user and password separately like in
  60. curl -u name:passwd http://machine.domain/full/path/to/file
  61. HTTP offers many different methods of authentication and curl supports
  62. several: Basic, Digest, NTLM and Negotiate. Without telling which method to
  63. use, curl defaults to Basic. You can also ask curl to pick the most secure
  64. ones out of the ones that the server accepts for the given URL, by using
  65. --anyauth.
  66. NOTE! Since HTTP URLs don't support user and password, you can't use that
  67. style when using Curl via a proxy. You _must_ use the -u style fetch
  68. during such circumstances.
  69. HTTPS
  70. Probably most commonly used with private certificates, as explained below.
  71. PROXY
  72. Get an ftp file using a proxy named my-proxy that uses port 888:
  73. curl -x my-proxy:888 ftp://ftp.leachsite.com/README
  74. Get a file from a HTTP server that requires user and password, using the
  75. same proxy as above:
  76. curl -u user:passwd -x my-proxy:888 http://www.get.this/
  77. Some proxies require special authentication. Specify by using -U as above:
  78. curl -U user:passwd -x my-proxy:888 http://www.get.this/
  79. curl also supports SOCKS4 and SOCKS5 proxies with --socks4 and --socks5.
  80. See also the environment variables Curl support that offer further proxy
  81. control.
  82. RANGES
  83. With HTTP 1.1 byte-ranges were introduced. Using this, a client can request
  84. to get only one or more subparts of a specified document. Curl supports
  85. this with the -r flag.
  86. Get the first 100 bytes of a document:
  87. curl -r 0-99 http://www.get.this/
  88. Get the last 500 bytes of a document:
  89. curl -r -500 http://www.get.this/
  90. Curl also supports simple ranges for FTP files as well. Then you can only
  91. specify start and stop position.
  92. Get the first 100 bytes of a document using FTP:
  93. curl -r 0-99 ftp://www.get.this/README
  94. UPLOADING
  95. FTP / FTPS / SFTP / SCP
  96. Upload all data on stdin to a specified server:
  97. curl -T - ftp://ftp.upload.com/myfile
  98. Upload data from a specified file, login with user and password:
  99. curl -T uploadfile -u user:passwd ftp://ftp.upload.com/myfile
  100. Upload a local file to the remote site, and use the local file name remote
  101. too:
  102. curl -T uploadfile -u user:passwd ftp://ftp.upload.com/
  103. Upload a local file to get appended to the remote file:
  104. curl -T localfile -a ftp://ftp.upload.com/remotefile
  105. Curl also supports ftp upload through a proxy, but only if the proxy is
  106. configured to allow that kind of tunneling. If it does, you can run curl in
  107. a fashion similar to:
  108. curl --proxytunnel -x proxy:port -T localfile ftp.upload.com
  109. HTTP
  110. Upload all data on stdin to a specified http site:
  111. curl -T - http://www.upload.com/myfile
  112. Note that the http server must have been configured to accept PUT before
  113. this can be done successfully.
  114. For other ways to do http data upload, see the POST section below.
  115. VERBOSE / DEBUG
  116. If curl fails where it isn't supposed to, if the servers don't let you in,
  117. if you can't understand the responses: use the -v flag to get verbose
  118. fetching. Curl will output lots of info and what it sends and receives in
  119. order to let the user see all client-server interaction (but it won't show
  120. you the actual data).
  121. curl -v ftp://ftp.upload.com/
  122. To get even more details and information on what curl does, try using the
  123. --trace or --trace-ascii options with a given file name to log to, like
  124. this:
  125. curl --trace trace.txt www.haxx.se
  126. DETAILED INFORMATION
  127. Different protocols provide different ways of getting detailed information
  128. about specific files/documents. To get curl to show detailed information
  129. about a single file, you should use -I/--head option. It displays all
  130. available info on a single file for HTTP and FTP. The HTTP information is a
  131. lot more extensive.
  132. For HTTP, you can get the header information (the same as -I would show)
  133. shown before the data by using -i/--include. Curl understands the
  134. -D/--dump-header option when getting files from both FTP and HTTP, and it
  135. will then store the headers in the specified file.
  136. Store the HTTP headers in a separate file (headers.txt in the example):
  137. curl --dump-header headers.txt curl.haxx.se
  138. Note that headers stored in a separate file can be very useful at a later
  139. time if you want curl to use cookies sent by the server. More about that in
  140. the cookies section.
  141. POST (HTTP)
  142. It's easy to post data using curl. This is done using the -d <data>
  143. option. The post data must be urlencoded.
  144. Post a simple "name" and "phone" guestbook.
  145. curl -d "name=Rafael%20Sagula&phone=3320780" \
  146. http://www.where.com/guest.cgi
  147. How to post a form with curl, lesson #1:
  148. Dig out all the <input> tags in the form that you want to fill in. (There's
  149. a perl program called formfind.pl on the curl site that helps with this).
  150. If there's a "normal" post, you use -d to post. -d takes a full "post
  151. string", which is in the format
  152. <variable1>=<data1>&<variable2>=<data2>&...
  153. The 'variable' names are the names set with "name=" in the <input> tags, and
  154. the data is the contents you want to fill in for the inputs. The data *must*
  155. be properly URL encoded. That means you replace space with + and that you
  156. write weird letters with %XX where XX is the hexadecimal representation of
  157. the letter's ASCII code.
  158. Example:
  159. (page located at http://www.formpost.com/getthis/
  160. <form action="post.cgi" method="post">
  161. <input name=user size=10>
  162. <input name=pass type=password size=10>
  163. <input name=id type=hidden value="blablabla">
  164. <input name=ding value="submit">
  165. </form>
  166. We want to enter user 'foobar' with password '12345'.
  167. To post to this, you enter a curl command line like:
  168. curl -d "user=foobar&pass=12345&id=blablabla&ding=submit" (continues)
  169. http://www.formpost.com/getthis/post.cgi
  170. While -d uses the application/x-www-form-urlencoded mime-type, generally
  171. understood by CGI's and similar, curl also supports the more capable
  172. multipart/form-data type. This latter type supports things like file upload.
  173. -F accepts parameters like -F "name=contents". If you want the contents to
  174. be read from a file, use <@filename> as contents. When specifying a file,
  175. you can also specify the file content type by appending ';type=<mime type>'
  176. to the file name. You can also post the contents of several files in one
  177. field. For example, the field name 'coolfiles' is used to send three files,
  178. with different content types using the following syntax:
  179. curl -F "coolfiles=@fil1.gif;type=image/gif,fil2.txt,fil3.html" \
  180. http://www.post.com/postit.cgi
  181. If the content-type is not specified, curl will try to guess from the file
  182. extension (it only knows a few), or use the previously specified type (from
  183. an earlier file if several files are specified in a list) or else it will
  184. using the default type 'text/plain'.
  185. Emulate a fill-in form with -F. Let's say you fill in three fields in a
  186. form. One field is a file name which to post, one field is your name and one
  187. field is a file description. We want to post the file we have written named
  188. "cooltext.txt". To let curl do the posting of this data instead of your
  189. favourite browser, you have to read the HTML source of the form page and
  190. find the names of the input fields. In our example, the input field names
  191. are 'file', 'yourname' and 'filedescription'.
  192. curl -F "file=@cooltext.txt" -F "yourname=Daniel" \
  193. -F "filedescription=Cool text file with cool text inside" \
  194. http://www.post.com/postit.cgi
  195. To send two files in one post you can do it in two ways:
  196. 1. Send multiple files in a single "field" with a single field name:
  197. curl -F "pictures=@dog.gif,cat.gif"
  198. 2. Send two fields with two field names:
  199. curl -F "docpicture=@dog.gif" -F "catpicture=@cat.gif"
  200. To send a field value literally without interpreting a leading '@'
  201. or '<', or an embedded ';type=', use --form-string instead of
  202. -F. This is recommended when the value is obtained from a user or
  203. some other unpredictable source. Under these circumstances, using
  204. -F instead of --form-string would allow a user to trick curl into
  205. uploading a file.
  206. REFERRER
  207. A HTTP request has the option to include information about which address
  208. that referred to actual page. Curl allows you to specify the
  209. referrer to be used on the command line. It is especially useful to
  210. fool or trick stupid servers or CGI scripts that rely on that information
  211. being available or contain certain data.
  212. curl -e www.coolsite.com http://www.showme.com/
  213. NOTE: The Referer: [sic] field is defined in the HTTP spec to be a full URL.
  214. USER AGENT
  215. A HTTP request has the option to include information about the browser
  216. that generated the request. Curl allows it to be specified on the command
  217. line. It is especially useful to fool or trick stupid servers or CGI
  218. scripts that only accept certain browsers.
  219. Example:
  220. curl -A 'Mozilla/3.0 (Win95; I)' http://www.nationsbank.com/
  221. Other common strings:
  222. 'Mozilla/3.0 (Win95; I)' Netscape Version 3 for Windows 95
  223. 'Mozilla/3.04 (Win95; U)' Netscape Version 3 for Windows 95
  224. 'Mozilla/2.02 (OS/2; U)' Netscape Version 2 for OS/2
  225. 'Mozilla/4.04 [en] (X11; U; AIX 4.2; Nav)' NS for AIX
  226. 'Mozilla/4.05 [en] (X11; U; Linux 2.0.32 i586)' NS for Linux
  227. Note that Internet Explorer tries hard to be compatible in every way:
  228. 'Mozilla/4.0 (compatible; MSIE 4.01; Windows 95)' MSIE for W95
  229. Mozilla is not the only possible User-Agent name:
  230. 'Konqueror/1.0' KDE File Manager desktop client
  231. 'Lynx/2.7.1 libwww-FM/2.14' Lynx command line browser
  232. COOKIES
  233. Cookies are generally used by web servers to keep state information at the
  234. client's side. The server sets cookies by sending a response line in the
  235. headers that looks like 'Set-Cookie: <data>' where the data part then
  236. typically contains a set of NAME=VALUE pairs (separated by semicolons ';'
  237. like "NAME1=VALUE1; NAME2=VALUE2;"). The server can also specify for what
  238. path the "cookie" should be used for (by specifying "path=value"), when the
  239. cookie should expire ("expire=DATE"), for what domain to use it
  240. ("domain=NAME") and if it should be used on secure connections only
  241. ("secure").
  242. If you've received a page from a server that contains a header like:
  243. Set-Cookie: sessionid=boo123; path="/foo";
  244. it means the server wants that first pair passed on when we get anything in
  245. a path beginning with "/foo".
  246. Example, get a page that wants my name passed in a cookie:
  247. curl -b "name=Daniel" www.sillypage.com
  248. Curl also has the ability to use previously received cookies in following
  249. sessions. If you get cookies from a server and store them in a file in a
  250. manner similar to:
  251. curl --dump-header headers www.example.com
  252. ... you can then in a second connect to that (or another) site, use the
  253. cookies from the 'headers' file like:
  254. curl -b headers www.example.com
  255. While saving headers to a file is a working way to store cookies, it is
  256. however error-prone and not the preferred way to do this. Instead, make curl
  257. save the incoming cookies using the well-known netscape cookie format like
  258. this:
  259. curl -c cookies.txt www.example.com
  260. Note that by specifying -b you enable the "cookie awareness" and with -L
  261. you can make curl follow a location: (which often is used in combination
  262. with cookies). So that if a site sends cookies and a location, you can
  263. use a non-existing file to trigger the cookie awareness like:
  264. curl -L -b empty.txt www.example.com
  265. The file to read cookies from must be formatted using plain HTTP headers OR
  266. as netscape's cookie file. Curl will determine what kind it is based on the
  267. file contents. In the above command, curl will parse the header and store
  268. the cookies received from www.example.com. curl will send to the server the
  269. stored cookies which match the request as it follows the location. The
  270. file "empty.txt" may be a nonexistent file.
  271. Alas, to both read and write cookies from a netscape cookie file, you can
  272. set both -b and -c to use the same file:
  273. curl -b cookies.txt -c cookies.txt www.example.com
  274. PROGRESS METER
  275. The progress meter exists to show a user that something actually is
  276. happening. The different fields in the output have the following meaning:
  277. % Total % Received % Xferd Average Speed Time Curr.
  278. Dload Upload Total Current Left Speed
  279. 0 151M 0 38608 0 0 9406 0 4:41:43 0:00:04 4:41:39 9287
  280. From left-to-right:
  281. % - percentage completed of the whole transfer
  282. Total - total size of the whole expected transfer
  283. % - percentage completed of the download
  284. Received - currently downloaded amount of bytes
  285. % - percentage completed of the upload
  286. Xferd - currently uploaded amount of bytes
  287. Average Speed
  288. Dload - the average transfer speed of the download
  289. Average Speed
  290. Upload - the average transfer speed of the upload
  291. Time Total - expected time to complete the operation
  292. Time Current - time passed since the invoke
  293. Time Left - expected time left to completion
  294. Curr.Speed - the average transfer speed the last 5 seconds (the first
  295. 5 seconds of a transfer is based on less time of course.)
  296. The -# option will display a totally different progress bar that doesn't
  297. need much explanation!
  298. SPEED LIMIT
  299. Curl allows the user to set the transfer speed conditions that must be met
  300. to let the transfer keep going. By using the switch -y and -Y you
  301. can make curl abort transfers if the transfer speed is below the specified
  302. lowest limit for a specified time.
  303. To have curl abort the download if the speed is slower than 3000 bytes per
  304. second for 1 minute, run:
  305. curl -Y 3000 -y 60 www.far-away-site.com
  306. This can very well be used in combination with the overall time limit, so
  307. that the above operation must be completed in whole within 30 minutes:
  308. curl -m 1800 -Y 3000 -y 60 www.far-away-site.com
  309. Forcing curl not to transfer data faster than a given rate is also possible,
  310. which might be useful if you're using a limited bandwidth connection and you
  311. don't want your transfer to use all of it (sometimes referred to as
  312. "bandwidth throttle").
  313. Make curl transfer data no faster than 10 kilobytes per second:
  314. curl --limit-rate 10K www.far-away-site.com
  315. or
  316. curl --limit-rate 10240 www.far-away-site.com
  317. Or prevent curl from uploading data faster than 1 megabyte per second:
  318. curl -T upload --limit-rate 1M ftp://uploadshereplease.com
  319. When using the --limit-rate option, the transfer rate is regulated on a
  320. per-second basis, which will cause the total transfer speed to become lower
  321. than the given number. Sometimes of course substantially lower, if your
  322. transfer stalls during periods.
  323. CONFIG FILE
  324. Curl automatically tries to read the .curlrc file (or _curlrc file on win32
  325. systems) from the user's home dir on startup.
  326. The config file could be made up with normal command line switches, but you
  327. can also specify the long options without the dashes to make it more
  328. readable. You can separate the options and the parameter with spaces, or
  329. with = or :. Comments can be used within the file. If the first letter on a
  330. line is a '#'-letter the rest of the line is treated as a comment.
  331. If you want the parameter to contain spaces, you must enclose the entire
  332. parameter within double quotes ("). Within those quotes, you specify a
  333. quote as \".
  334. NOTE: You must specify options and their arguments on the same line.
  335. Example, set default time out and proxy in a config file:
  336. # We want a 30 minute timeout:
  337. -m 1800
  338. # ... and we use a proxy for all accesses:
  339. proxy = proxy.our.domain.com:8080
  340. White spaces ARE significant at the end of lines, but all white spaces
  341. leading up to the first characters of each line are ignored.
  342. Prevent curl from reading the default file by using -q as the first command
  343. line parameter, like:
  344. curl -q www.thatsite.com
  345. Force curl to get and display a local help page in case it is invoked
  346. without URL by making a config file similar to:
  347. # default url to get
  348. url = "http://help.with.curl.com/curlhelp.html"
  349. You can specify another config file to be read by using the -K/--config
  350. flag. If you set config file name to "-" it'll read the config from stdin,
  351. which can be handy if you want to hide options from being visible in process
  352. tables etc:
  353. echo "user = user:passwd" | curl -K - http://that.secret.site.com
  354. EXTRA HEADERS
  355. When using curl in your own very special programs, you may end up needing
  356. to pass on your own custom headers when getting a web page. You can do
  357. this by using the -H flag.
  358. Example, send the header "X-you-and-me: yes" to the server when getting a
  359. page:
  360. curl -H "X-you-and-me: yes" www.love.com
  361. This can also be useful in case you want curl to send a different text in a
  362. header than it normally does. The -H header you specify then replaces the
  363. header curl would normally send. If you replace an internal header with an
  364. empty one, you prevent that header from being sent. To prevent the Host:
  365. header from being used:
  366. curl -H "Host:" www.server.com
  367. FTP and PATH NAMES
  368. Do note that when getting files with the ftp:// URL, the given path is
  369. relative the directory you enter. To get the file 'README' from your home
  370. directory at your ftp site, do:
  371. curl ftp://user:passwd@my.site.com/README
  372. But if you want the README file from the root directory of that very same
  373. site, you need to specify the absolute file name:
  374. curl ftp://user:passwd@my.site.com//README
  375. (I.e with an extra slash in front of the file name.)
  376. SFTP and SCP and PATH NAMES
  377. With sftp: and scp: URLs, the path name given is the absolute name on the
  378. server. To access a file relative to the remote user's home directory,
  379. prefix the file with /~/ , such as:
  380. curl -u $USER sftp://home.example.com/~/.bashrc
  381. FTP and firewalls
  382. The FTP protocol requires one of the involved parties to open a second
  383. connection as soon as data is about to get transfered. There are two ways to
  384. do this.
  385. The default way for curl is to issue the PASV command which causes the
  386. server to open another port and await another connection performed by the
  387. client. This is good if the client is behind a firewall that don't allow
  388. incoming connections.
  389. curl ftp.download.com
  390. If the server for example, is behind a firewall that don't allow connections
  391. on other ports than 21 (or if it just doesn't support the PASV command), the
  392. other way to do it is to use the PORT command and instruct the server to
  393. connect to the client on the given (as parameters to the PORT command) IP
  394. number and port.
  395. The -P flag to curl supports a few different options. Your machine may have
  396. several IP-addresses and/or network interfaces and curl allows you to select
  397. which of them to use. Default address can also be used:
  398. curl -P - ftp.download.com
  399. Download with PORT but use the IP address of our 'le0' interface (this does
  400. not work on windows):
  401. curl -P le0 ftp.download.com
  402. Download with PORT but use 192.168.0.10 as our IP address to use:
  403. curl -P 192.168.0.10 ftp.download.com
  404. NETWORK INTERFACE
  405. Get a web page from a server using a specified port for the interface:
  406. curl --interface eth0:1 http://www.netscape.com/
  407. or
  408. curl --interface 192.168.1.10 http://www.netscape.com/
  409. HTTPS
  410. Secure HTTP requires SSL libraries to be installed and used when curl is
  411. built. If that is done, curl is capable of retrieving and posting documents
  412. using the HTTPS protocol.
  413. Example:
  414. curl https://www.secure-site.com
  415. Curl is also capable of using your personal certificates to get/post files
  416. from sites that require valid certificates. The only drawback is that the
  417. certificate needs to be in PEM-format. PEM is a standard and open format to
  418. store certificates with, but it is not used by the most commonly used
  419. browsers (Netscape and MSIE both use the so called PKCS#12 format). If you
  420. want curl to use the certificates you use with your (favourite) browser, you
  421. may need to download/compile a converter that can convert your browser's
  422. formatted certificates to PEM formatted ones. This kind of converter is
  423. included in recent versions of OpenSSL, and for older versions Dr Stephen
  424. N. Henson has written a patch for SSLeay that adds this functionality. You
  425. can get his patch (that requires an SSLeay installation) from his site at:
  426. http://www.drh-consultancy.demon.co.uk/
  427. Example on how to automatically retrieve a document using a certificate with
  428. a personal password:
  429. curl -E /path/to/cert.pem:password https://secure.site.com/
  430. If you neglect to specify the password on the command line, you will be
  431. prompted for the correct password before any data can be received.
  432. Many older SSL-servers have problems with SSLv3 or TLS, that newer versions
  433. of OpenSSL etc is using, therefore it is sometimes useful to specify what
  434. SSL-version curl should use. Use -3, -2 or -1 to specify that exact SSL
  435. version to use (for SSLv3, SSLv2 or TLSv1 respectively):
  436. curl -2 https://secure.site.com/
  437. Otherwise, curl will first attempt to use v3 and then v2.
  438. To use OpenSSL to convert your favourite browser's certificate into a PEM
  439. formatted one that curl can use, do something like this (assuming netscape,
  440. but IE is likely to work similarly):
  441. You start with hitting the 'security' menu button in netscape.
  442. Select 'certificates->yours' and then pick a certificate in the list
  443. Press the 'export' button
  444. enter your PIN code for the certs
  445. select a proper place to save it
  446. Run the 'openssl' application to convert the certificate. If you cd to the
  447. openssl installation, you can do it like:
  448. # ./apps/openssl pkcs12 -in [file you saved] -clcerts -out [PEMfile]
  449. RESUMING FILE TRANSFERS
  450. To continue a file transfer where it was previously aborted, curl supports
  451. resume on http(s) downloads as well as ftp uploads and downloads.
  452. Continue downloading a document:
  453. curl -C - -o file ftp://ftp.server.com/path/file
  454. Continue uploading a document(*1):
  455. curl -C - -T file ftp://ftp.server.com/path/file
  456. Continue downloading a document from a web server(*2):
  457. curl -C - -o file http://www.server.com/
  458. (*1) = This requires that the ftp server supports the non-standard command
  459. SIZE. If it doesn't, curl will say so.
  460. (*2) = This requires that the web server supports at least HTTP/1.1. If it
  461. doesn't, curl will say so.
  462. TIME CONDITIONS
  463. HTTP allows a client to specify a time condition for the document it
  464. requests. It is If-Modified-Since or If-Unmodified-Since. Curl allow you to
  465. specify them with the -z/--time-cond flag.
  466. For example, you can easily make a download that only gets performed if the
  467. remote file is newer than a local copy. It would be made like:
  468. curl -z local.html http://remote.server.com/remote.html
  469. Or you can download a file only if the local file is newer than the remote
  470. one. Do this by prepending the date string with a '-', as in:
  471. curl -z -local.html http://remote.server.com/remote.html
  472. You can specify a "free text" date as condition. Tell curl to only download
  473. the file if it was updated since January 12, 2012:
  474. curl -z "Jan 12 2012" http://remote.server.com/remote.html
  475. Curl will then accept a wide range of date formats. You always make the date
  476. check the other way around by prepending it with a dash '-'.
  477. DICT
  478. For fun try
  479. curl dict://dict.org/m:curl
  480. curl dict://dict.org/d:heisenbug:jargon
  481. curl dict://dict.org/d:daniel:web1913
  482. Aliases for 'm' are 'match' and 'find', and aliases for 'd' are 'define'
  483. and 'lookup'. For example,
  484. curl dict://dict.org/find:curl
  485. Commands that break the URL description of the RFC (but not the DICT
  486. protocol) are
  487. curl dict://dict.org/show:db
  488. curl dict://dict.org/show:strat
  489. Authentication is still missing (but this is not required by the RFC)
  490. LDAP
  491. If you have installed the OpenLDAP library, curl can take advantage of it
  492. and offer ldap:// support.
  493. LDAP is a complex thing and writing an LDAP query is not an easy task. I do
  494. advice you to dig up the syntax description for that elsewhere. Two places
  495. that might suit you are:
  496. Netscape's "Netscape Directory SDK 3.0 for C Programmer's Guide Chapter 10:
  497. Working with LDAP URLs":
  498. http://developer.netscape.com/docs/manuals/dirsdk/csdk30/url.htm
  499. RFC 2255, "The LDAP URL Format" http://curl.haxx.se/rfc/rfc2255.txt
  500. To show you an example, this is now I can get all people from my local LDAP
  501. server that has a certain sub-domain in their email address:
  502. curl -B "ldap://ldap.frontec.se/o=frontec??sub?mail=*sth.frontec.se"
  503. If I want the same info in HTML format, I can get it by not using the -B
  504. (enforce ASCII) flag.
  505. ENVIRONMENT VARIABLES
  506. Curl reads and understands the following environment variables:
  507. http_proxy, HTTPS_PROXY, FTP_PROXY
  508. They should be set for protocol-specific proxies. General proxy should be
  509. set with
  510. ALL_PROXY
  511. A comma-separated list of host names that shouldn't go through any proxy is
  512. set in (only an asterisk, '*' matches all hosts)
  513. NO_PROXY
  514. If a tail substring of the domain-path for a host matches one of these
  515. strings, transactions with that node will not be proxied.
  516. The usage of the -x/--proxy flag overrides the environment variables.
  517. NETRC
  518. Unix introduced the .netrc concept a long time ago. It is a way for a user
  519. to specify name and password for commonly visited ftp sites in a file so
  520. that you don't have to type them in each time you visit those sites. You
  521. realize this is a big security risk if someone else gets hold of your
  522. passwords, so therefore most unix programs won't read this file unless it is
  523. only readable by yourself (curl doesn't care though).
  524. Curl supports .netrc files if told so (using the -n/--netrc and
  525. --netrc-optional options). This is not restricted to only ftp,
  526. but curl can use it for all protocols where authentication is used.
  527. A very simple .netrc file could look something like:
  528. machine curl.haxx.se login iamdaniel password mysecret
  529. CUSTOM OUTPUT
  530. To better allow script programmers to get to know about the progress of
  531. curl, the -w/--write-out option was introduced. Using this, you can specify
  532. what information from the previous transfer you want to extract.
  533. To display the amount of bytes downloaded together with some text and an
  534. ending newline:
  535. curl -w 'We downloaded %{size_download} bytes\n' www.download.com
  536. KERBEROS FTP TRANSFER
  537. Curl supports kerberos4 and kerberos5/GSSAPI for FTP transfers. You need
  538. the kerberos package installed and used at curl build time for it to be
  539. used.
  540. First, get the krb-ticket the normal way, like with the kinit/kauth tool.
  541. Then use curl in way similar to:
  542. curl --krb private ftp://krb4site.com -u username:fakepwd
  543. There's no use for a password on the -u switch, but a blank one will make
  544. curl ask for one and you already entered the real password to kinit/kauth.
  545. TELNET
  546. The curl telnet support is basic and very easy to use. Curl passes all data
  547. passed to it on stdin to the remote server. Connect to a remote telnet
  548. server using a command line similar to:
  549. curl telnet://remote.server.com
  550. And enter the data to pass to the server on stdin. The result will be sent
  551. to stdout or to the file you specify with -o.
  552. You might want the -N/--no-buffer option to switch off the buffered output
  553. for slow connections or similar.
  554. Pass options to the telnet protocol negotiation, by using the -t option. To
  555. tell the server we use a vt100 terminal, try something like:
  556. curl -tTTYPE=vt100 telnet://remote.server.com
  557. Other interesting options for it -t include:
  558. - XDISPLOC=<X display> Sets the X display location.
  559. - NEW_ENV=<var,val> Sets an environment variable.
  560. NOTE: the telnet protocol does not specify any way to login with a specified
  561. user and password so curl can't do that automatically. To do that, you need
  562. to track when the login prompt is received and send the username and
  563. password accordingly.
  564. PERSISTENT CONNECTIONS
  565. Specifying multiple files on a single command line will make curl transfer
  566. all of them, one after the other in the specified order.
  567. libcurl will attempt to use persistent connections for the transfers so that
  568. the second transfer to the same host can use the same connection that was
  569. already initiated and was left open in the previous transfer. This greatly
  570. decreases connection time for all but the first transfer and it makes a far
  571. better use of the network.
  572. Note that curl cannot use persistent connections for transfers that are used
  573. in subsequence curl invokes. Try to stuff as many URLs as possible on the
  574. same command line if they are using the same host, as that'll make the
  575. transfers faster. If you use a http proxy for file transfers, practically
  576. all transfers will be persistent.
  577. MULTIPLE TRANSFERS WITH A SINGLE COMMAND LINE
  578. As is mentioned above, you can download multiple files with one command line
  579. by simply adding more URLs. If you want those to get saved to a local file
  580. instead of just printed to stdout, you need to add one save option for each
  581. URL you specify. Note that this also goes for the -O option (but not
  582. --remote-name-all).
  583. For example: get two files and use -O for the first and a custom file
  584. name for the second:
  585. curl -O http://url.com/file.txt ftp://ftp.com/moo.exe -o moo.jpg
  586. You can also upload multiple files in a similar fashion:
  587. curl -T local1 ftp://ftp.com/moo.exe -T local2 ftp://ftp.com/moo2.txt
  588. IPv6
  589. curl will connect to a server with IPv6 when a host lookup returns an IPv6
  590. address and fall back to IPv4 if the connection fails. The --ipv4 and --ipv6
  591. options can specify which address to use when both are available. IPv6
  592. addresses can also be specified directly in URLs using the syntax:
  593. http://[2001:1890:1112:1::20]/overview.html
  594. When this style is used, the -g option must be given to stop curl from
  595. interpreting the square brackets as special globbing characters. Link local
  596. and site local addresses including a scope identifier, such as fe80::1234%1,
  597. may also be used, but the scope portion must be numeric and the percent
  598. character must be URL escaped. The previous example in an SFTP URL might
  599. look like:
  600. sftp://[fe80::1234%251]/
  601. IPv6 addresses provided other than in URLs (e.g. to the --proxy, --interface
  602. or --ftp-port options) should not be URL encoded.
  603. MAILING LISTS
  604. For your convenience, we have several open mailing lists to discuss curl,
  605. its development and things relevant to this. Get all info at
  606. http://curl.haxx.se/mail/. Some of the lists available are:
  607. curl-users
  608. Users of the command line tool. How to use it, what doesn't work, new
  609. features, related tools, questions, news, installations, compilations,
  610. running, porting etc.
  611. curl-library
  612. Developers using or developing libcurl. Bugs, extensions, improvements.
  613. curl-announce
  614. Low-traffic. Only receives announcements of new public versions. At worst,
  615. that makes something like one or two mails per month, but usually only one
  616. mail every second month.
  617. curl-and-php
  618. Using the curl functions in PHP. Everything curl with a PHP angle. Or PHP
  619. with a curl angle.
  620. curl-and-python
  621. Python hackers using curl with or without the python binding pycurl.
  622. Please direct curl questions, feature requests and trouble reports to one of
  623. these mailing lists instead of mailing any individual.