FAQ 45 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113
  1. Updated: November 2, 2005 (http://curl.haxx.se/docs/faq.html)
  2. _ _ ____ _
  3. ___| | | | _ \| |
  4. / __| | | | |_) | |
  5. | (__| |_| | _ <| |___
  6. \___|\___/|_| \_\_____|
  7. FAQ
  8. 1. Philosophy
  9. 1.1 What is cURL?
  10. 1.2 What is libcurl?
  11. 1.3 What is curl not?
  12. 1.4 When will you make curl do XXXX ?
  13. 1.5 Who makes curl?
  14. 1.6 What do you get for making curl?
  15. 1.7 What about CURL from curl.com?
  16. 1.8 I have a problem who do I mail?
  17. 1.9 Where do I buy commercial support for curl?
  18. 1.10 How many are using curl?
  19. 2. Install Related Problems
  20. 2.1 configure doesn't find OpenSSL even when it is installed
  21. 2.1.1 native linker doesn't find OpenSSL
  22. 2.1.2 only the libssl lib is missing
  23. 2.2 Does curl work/build with other SSL libraries?
  24. 2.3 Where can I find a copy of LIBEAY32.DLL?
  25. 2.4 Does curl support Socks (RFC 1928) ?
  26. 3. Usage Problems
  27. 3.1 curl: (1) SSL is disabled, https: not supported
  28. 3.2 How do I tell curl to resume a transfer?
  29. 3.3 Why doesn't my posting using -F work?
  30. 3.4 How do I tell curl to run custom FTP commands?
  31. 3.5 How can I disable the Pragma: nocache header?
  32. 3.6 Does curl support ASP, XML, XHTML or HTML version Y?
  33. 3.7 Can I use curl to delete/rename a file through FTP?
  34. 3.8 How do I tell curl to follow HTTP redirects?
  35. 3.9 How do I use curl in my favorite programming language?
  36. 3.10 What about SOAP, WebDAV, XML-RPC or similar protocols over HTTP?
  37. 3.11 How do I POST with a different Content-Type?
  38. 3.12 Why do FTP specific features over HTTP proxy fail?
  39. 3.13 Why does my single/double quotes fail?
  40. 3.14 Does curl support javascript or pac (automated proxy config)?
  41. 3.15 Can I do recursive fetches with curl?
  42. 3.16 What certificates do I need when I use SSL?
  43. 3.17 How do I list the root dir of an FTP server?
  44. 3.18 Can I use curl to send a POST/PUT and not wait for a response?
  45. 4. Running Problems
  46. 4.1 Problems connecting to SSL servers.
  47. 4.2 Why do I get problems when I use & or % in the URL?
  48. 4.3 How can I use {, }, [ or ] to specify multiple URLs?
  49. 4.4 Why do I get downloaded data even though the web page doesn't exist?
  50. 4.5 Why do I get return code XXX from a HTTP server?
  51. 4.5.1 "400 Bad Request"
  52. 4.5.2 "401 Unauthorized"
  53. 4.5.3 "403 Forbidden"
  54. 4.5.4 "404 Not Found"
  55. 4.5.5 "405 Method Not Allowed"
  56. 4.5.6 "301 Moved Permanently"
  57. 4.6 Can you tell me what error code 142 means?
  58. 4.7 How do I keep user names and passwords secret in Curl command lines?
  59. 4.8 I found a bug!
  60. 4.9 Curl can't authenticate to the server that requires NTLM?
  61. 4.10 My HTTP request using HEAD, PUT or DELETE doesn't work!
  62. 4.11 Why does my HTTP range requests return the full document?
  63. 4.12 Why do I get "certificate verify failed" ?
  64. 4.13 Why is curl -R on Windows one hour off?
  65. 4.14 Redirects work in browser but not with curl!
  66. 5. libcurl Issues
  67. 5.1 Is libcurl thread-safe?
  68. 5.2 How can I receive all data into a large memory chunk?
  69. 5.3 How do I fetch multiple files with libcurl?
  70. 5.4 Does libcurl do Winsock initing on win32 systems?
  71. 5.5 Does CURLOPT_WRITEDATA and CURLOPT_READDATA work on win32 ?
  72. 5.6 What about Keep-Alive or persistent connections?
  73. 5.7 Link errors when building libcurl on Windows!
  74. 5.8 libcurl.so.3: open failed: No such file or directory
  75. 5.9 How does libcurl resolve host names?
  76. 5.10 How do I prevent libcurl from writing the response to stdout?
  77. 5.11 How do I make libcurl not receive the whole HTTP response?
  78. 5.12 Can I make libcurl fake or hide my real IP address?
  79. 6. License Issues
  80. 6.1 I have a GPL program, can I use the libcurl library?
  81. 6.2 I have a closed-source program, can I use the libcurl library?
  82. 6.3 I have a BSD licensed program, can I use the libcurl library?
  83. 6.4 I have a program that uses LGPL libraries, can I use libcurl?
  84. 6.5 Can I modify curl/libcurl for my program and keep the changes secret?
  85. 6.6 Can you please change the curl/libcurl license to XXXX?
  86. 6.7 What are my obligations when using libcurl in my commerical apps?
  87. 7. PHP/CURL Issues
  88. 7.1 What is PHP/CURL?
  89. 7.2 Who write PHP/CURL?
  90. 7.3 Can I perform multiple requests using the same handle?
  91. ==============================================================================
  92. 1. Philosophy
  93. 1.1 What is cURL?
  94. cURL is the name of the project. The name is a play on 'Client for URLs',
  95. originally with URL spelled in uppercase to make it obvious it deals with
  96. URLs. The fact it can also be pronounced 'see URL' also helped, it works as
  97. an abbreviation for "Client URL Request Library" or why not the recursive
  98. version: "Curl URL Request Library".
  99. The cURL project produces two products:
  100. libcurl
  101. A free and easy-to-use client-side URL transfer library, supporting FTP,
  102. FTPS, HTTP, HTTPS, TELNET, DICT, FILE and LDAP. libcurl supports
  103. HTTPS certificates, HTTP POST, HTTP PUT, FTP uploading, kerberos, HTTP
  104. form based upload, proxies, cookies, user+password authentication, file
  105. transfer resume, http proxy tunneling and more!
  106. libcurl is highly portable, it builds and works identically on numerous
  107. platforms, including Solaris, NetBSD, FreeBSD, OpenBSD, Darwin, HPUX,
  108. IRIX, AIX, Tru64, Linux, UnixWare, HURD, Windows, Amiga, OS/2, BeOs, Mac
  109. OS X, Ultrix, QNX, OpenVMS, RISC OS, Novell NetWare, DOS and more...
  110. libcurl is free, thread-safe, IPv6 compatible, feature rich, well
  111. supported and fast.
  112. curl
  113. A command line tool for getting or sending files using URL syntax.
  114. Since curl uses libcurl, it supports a range of common Internet protocols,
  115. currently including HTTP, HTTPS, FTP, FTPS, LDAP, DICT, TELNET and FILE.
  116. We pronounce curl and cURL with an initial k sound: [kurl].
  117. There are numerous sub-projects and related projects that also use the word
  118. curl in the project names in various combinations, but you should take
  119. notice that this FAQ is directed at the command-line tool named curl (and
  120. libcurl the library), and may therefore not be valid for other curl-related
  121. projects. (There is however a small section for the PHP/CURL in this FAQ.)
  122. 1.2 What is libcurl?
  123. libcurl is a reliable and portable library which provides you with an easy
  124. interface to a range of common Internet protocols.
  125. You can use libcurl for free in your application, be it open source,
  126. commercial or closed-source.
  127. libcurl is most probably the most portable, most powerful and most often
  128. used C-based multi-platform file transfer library on this planet - be it
  129. open source or commercial.
  130. 1.3 What is curl not?
  131. Curl is *not* a wget clone. That is a common misconception. Never, during
  132. curl's development, have we intended curl to replace wget or compete on its
  133. market. Curl is targeted at single-shot file transfers.
  134. Curl is not a web site mirroring program. If you want to use curl to mirror
  135. something: fine, go ahead and write a script that wraps around curl to make
  136. it reality (like curlmirror.pl does).
  137. Curl is not an FTP site mirroring program. Sure, get and send FTP with curl
  138. but if you want systematic and sequential behavior you should write a
  139. script (or write a new program that interfaces libcurl) and do it.
  140. Curl is not a PHP tool, even though it works perfectly well when used from
  141. or with PHP (when using the PHP/CURL module).
  142. Curl is not a single-OS program. Curl exists, compiles, builds and runs
  143. under a wide range of operating systems, including all modern Unixes (and a
  144. bunch of older ones too), Windows, Amiga, BeOS, OS/2, OS X, QNX etc.
  145. 1.4 When will you make curl do XXXX ?
  146. We love suggestions of what to change in order to make curl and libcurl
  147. better. We do however believe in a few rules when it comes to the future of
  148. curl:
  149. * Curl -- the command line tool -- is to remain a non-graphical command line
  150. tool. If you want GUIs or fancy scripting capabilities, you should look
  151. for another tool that uses libcurl.
  152. * We do not add things to curl that other small and available tools already
  153. do very fine at the side. Curl's output is fine to pipe into another
  154. program or redirect to another file for the next program to interpret.
  155. * We focus on protocol related issues and improvements. If you wanna do more
  156. magic with the supported protocols than curl currently does, chances are
  157. big we will agree. If you wanna add more protocols, we may very well
  158. agree.
  159. * If you want someone else to make all the work while you wait for us to
  160. implement it for you, that is not a very friendly attitude. We spend a
  161. considerable time already on maintaining and developing curl. In order to
  162. get more out of us, you should consider trading in some of your time and
  163. efforts in return.
  164. * If you write the code, chances are bigger that it will get into curl
  165. faster.
  166. 1.5 Who makes curl?
  167. curl and libcurl are not made by any single individual. Daniel Stenberg is
  168. project leader and main developer, but other persons' submissions are
  169. important and crucial. Anyone can contribute and post their changes and
  170. improvements and have them inserted in the main sources (of course on the
  171. condition that developers agree on that the fixes are good).
  172. The full list of the more than 450 contributors is found in the docs/THANKS
  173. file.
  174. curl is developed by a community, with Daniel at the wheel.
  175. 1.6 What do you get for making curl?
  176. Project cURL is entirely free and open. No person gets paid for developing
  177. (lib)curl. We do this voluntarily on our spare time.
  178. We get some help from companies. Contactor Data hosts the curl web site,
  179. Haxx owns the curl web site's domain and sourceforge.net hosts project
  180. services we take advantage from, like the bug tracker. Also, some companies
  181. have sponsored certain parts of the development in the past and I hope some
  182. will continue to do so in the future.
  183. If you want to support our project, consider a donation or a banner-program
  184. or even better: by helping us coding, documenting, testing etc.
  185. 1.7 What about CURL from curl.com?
  186. During the summer 2001, curl.com was busy advertising their client-side
  187. programming language for the web, named CURL.
  188. We are in no way associated with curl.com or their CURL programming
  189. language.
  190. Our project name curl has been in effective use since 1998. We were not the
  191. first computer related project to use the name "curl" and do not claim any
  192. first-hand rights to the name.
  193. We recognize that we will be living in parallel with curl.com and wish them
  194. every success.
  195. 1.8 I have a problem who do I mail?
  196. Please do not mail any single individual unless you really need to. Keep
  197. curl-related questions on a suitable mailing list. All available mailing
  198. lists are listed in the MANUAL document and online at
  199. http://curl.haxx.se/mail/
  200. Keeping curl-related questions and discussions on mailing lists allows
  201. others to join in and help, to share their ideas, contribute their
  202. suggestions and spread their wisdom. Keeping discussions on public mailing
  203. lists also allows for others to learn from this (both current and future
  204. users thanks to the web based archives of the mailing lists), thus saving us
  205. from having to repeat ourselves even more. Thanks for respecting this.
  206. If you have found or simply suspect a security problem in curl or libcurl,
  207. mail curl-security at haxx.se (closed list of receivers, mails are not
  208. disclosed) and tell. Then we can produce a fix in a timely manner before the
  209. flaw is announced to the world, thus lessen the impact the problem will have
  210. on existing users.
  211. 1.9 Where do I buy commercial support for curl?
  212. curl is fully open source. It means you can hire any skilled engineer to fix
  213. your curl-related problems.
  214. We list available alternatives on the curl web site:
  215. http://curl.haxx.se/support.html
  216. 1.10 How many are using curl?
  217. It is impossible to tell.
  218. We don't know how many users that knowingly have installed and use curl.
  219. We don't know how many users that use curl without knowing that they are in
  220. fact using it.
  221. We don't know how many users that downloaded or installed curl and then
  222. never use it.
  223. Some facts to use as input to the math:
  224. curl packages have been downloaded from the curl.haxx.se site well over a
  225. million times. curl is installed by default with most Linux
  226. distributions. curl is installed by default with Mac OS X. curl and libcurl
  227. as used by numerous applications that include libcurl binaries in their
  228. distribution packages (like Adobe Acrobat Reader and Google Earth).
  229. More than 40 known named companies use curl in commercial environments and
  230. products. More than 100 known named open source projects depend on
  231. (lib)curl.
  232. In a poll on the curl web site mid-2005, more than 50% of the 300+ answers
  233. estimated a user base of one million users or more.
  234. In March 2005, the "Linux Counter project" estimated a total Linux user base
  235. of some 29 millions, while Netcraft detected some 4 million "active" Linux
  236. based web servers. A guess is that a fair amount of these Linux
  237. installations have curl installed.
  238. http://curl.haxx.se/docs/companies.html
  239. http://curl.haxx.se/docs/programs.html
  240. http://curl.haxx.se/libcurl/using/apps.html
  241. http://counter.li.org/estimates.php
  242. http://news.netcraft.com/archives/2005/03/14/fedora_makes_rapid_progress.html
  243. 2. Install Related Problems
  244. 2.1 configure doesn't find OpenSSL even when it is installed
  245. This may be because of several reasons.
  246. 2.1.1 native linker doesn't find openssl
  247. Affected platforms:
  248. Solaris (native cc compiler)
  249. HPUX (native cc compiler)
  250. SGI IRIX (native cc compiler)
  251. SCO UNIX (native cc compiler)
  252. When configuring curl, I specify --with-ssl. OpenSSL is installed in
  253. /usr/local/ssl Configure reports SSL in /usr/local/ssl, but fails to find
  254. CRYPTO_lock in -lcrypto
  255. Cause: The cc for this test places the -L/usr/local/ssl/lib AFTER
  256. -lcrypto, so ld can't find the library. This is due to a bug in the GNU
  257. autoconf tool.
  258. Workaround: Specifying "LDFLAGS=-L/usr/local/ssl/lib" in front of
  259. ./configure places the -L/usr/local/ssl/lib early enough in the command
  260. line to make things work
  261. Solution submitted by: Bob Allison <allisonb@users.sourceforge.net>
  262. 2.1.2 only the libssl lib is missing
  263. If all include files and the libcrypto lib is present, with only the
  264. libssl being missing according to configure, this is mostly likely because
  265. a few functions are left out from the libssl.
  266. If the function names missing include RSA or RSAREF you can be certain
  267. that this is because libssl requires the RSA and RSAREF libs to build.
  268. See the INSTALL file section that explains how to add those libs to
  269. configure. Make sure that you remove the config.cache file before you
  270. rerun configure with the new flags.
  271. 2.2 Does curl work/build with other SSL libraries?
  272. Curl has been written to use OpenSSL or GnuTLS, although there should not be
  273. many problems using a different library. If anyone does "port" curl to use a
  274. different SSL library, we are of course very interested in getting the
  275. patch!
  276. 2.3 Where can I find a copy of LIBEAY32.DLL?
  277. That is an OpenSSL binary built for Windows.
  278. Curl uses OpenSSL to do the SSL stuff. The LIBEAY32.DLL is what curl needs
  279. on a windows machine to do https://. Check out the curl web site to find
  280. accurate and up-to-date pointers to recent OpenSSL DLLs and other binary
  281. packages.
  282. 2.4 Does curl support Socks (RFC 1928) ?
  283. Yes, SOCKS5 is supported.
  284. 3. Usage problems
  285. 3.1 curl: (1) SSL is disabled, https: not supported
  286. If you get this output when trying to get anything from a https:// server,
  287. it means that the configure script couldn't find all libs and include files
  288. it requires for SSL to work. If the configure script fails to find them,
  289. curl is simply built without SSL support.
  290. To get the https:// support into a curl that was previously built but that
  291. reports that https:// is not supported, you should dig through the document
  292. and logs and check out why the configure script doesn't find the SSL libs
  293. and/or include files.
  294. Also, check out the other paragraph in this FAQ labeled "configure doesn't
  295. find OpenSSL even when it is installed".
  296. 3.2 How do I tell curl to resume a transfer?
  297. Curl supports resumed transfers both ways on both FTP and HTTP.
  298. Try the -C option.
  299. 3.3 Why doesn't my posting using -F work?
  300. You can't simply use -F or -d at your choice. The web server that will
  301. receive your post assumes one of the formats. If the form you're trying to
  302. "fake" sets the type to 'multipart/form-data', then and only then you must
  303. use the -F type. In all the most common cases, you should use -d which then
  304. causes a posting with the type 'application/x-www-form-urlencoded'.
  305. This is described in some detail in the MANUAL and TheArtOfHttpScripting
  306. documents, and if you don't understand it the first time, read it again
  307. before you post questions about this to the mailing list. Also, try reading
  308. through the mailing list archives for old postings and questions regarding
  309. this.
  310. 3.4 How do I tell curl to run custom FTP commands?
  311. You can tell curl to perform optional commands both before and/or after a
  312. file transfer. Study the -Q/--quote option.
  313. Since curl is used for file transfers, you don't use curl to just perform
  314. FTP commands without transferring anything. Therefore you must always specify
  315. a URL to transfer to/from even when doing custom FTP commands.
  316. 3.5 How can I disable the Pragma: nocache header?
  317. You can change all internally generated headers by adding a replacement with
  318. the -H/--header option. By adding a header with empty contents you safely
  319. disable that one. Use -H "Pragma:" to disable that specific header.
  320. 3.6 Does curl support ASP, XML, XHTML or HTML version Y?
  321. To curl, all contents are alike. It doesn't matter how the page was
  322. generated. It may be ASP, PHP, Perl, shell-script, SSI or plain
  323. HTML-files. There's no difference to curl and it doesn't even know what kind
  324. of language that generated the page.
  325. See also item 3.14 regarding javascript.
  326. 3.7 Can I use curl to delete/rename a file through FTP?
  327. Yes. You specify custom FTP commands with -Q/--quote.
  328. One example would be to delete a file after you have downloaded it:
  329. curl -O ftp://download.com/coolfile -Q '-DELE coolfile'
  330. 3.8 How do I tell curl to follow HTTP redirects?
  331. Curl does not follow so-called redirects by default. The Location: header
  332. that informs the client about this is only interpreted if you're using the
  333. -L/--location option. As in:
  334. curl -L http://redirector.com
  335. Not all redirects are HTTP ones, see 4.14
  336. 3.9 How do I use curl in my favorite programming language?
  337. There exist many language interfaces/bindings for curl that integrates it
  338. better with various languages. If you are fluid in a script language, you
  339. may very well opt to use such an interface instead of using the command line
  340. tool.
  341. Find out more about which languages that support curl directly, and how to
  342. install and use them, in the libcurl section of the curl web site:
  343. http://curl.haxx.se/libcurl/
  344. In February 2003, there are interfaces available for the following
  345. languages: Basic, C, C++, Cocoa, Dylan, Euphoria, Java, Lua, Object-Pascal,
  346. Pascal, Perl, PHP, PostgreSQL, Python, Rexx, Ruby, Scheme and Tcl. By the
  347. time you read this, additional ones may have appeared!
  348. 3.10 What about SOAP, WebDAV, XML-RPC or similar protocols over HTTP?
  349. Curl adheres to the HTTP spec, which basically means you can play with *any*
  350. protocol that is built on top of HTTP. Protocols such as SOAP, WEBDAV and
  351. XML-RPC are all such ones. You can use -X to set custom requests and -H to
  352. set custom headers (or replace internally generated ones).
  353. Using libcurl is of course just as fine and you'd just use the proper
  354. library options to do the same.
  355. 3.11 How do I POST with a different Content-Type?
  356. You can always replace the internally generated headers with -H/--header.
  357. To make a simple HTTP POST with text/xml as content-type, do something like:
  358. curl -d "datatopost" -H "Content-Type: text/xml" [URL]
  359. 3.12 Why do FTP specific features over HTTP proxy fail?
  360. Because when you use a HTTP proxy, the protocol spoken on the network will
  361. be HTTP, even if you specify a FTP URL. This effectively means that you
  362. normally can't use FTP specific features such as FTP upload and FTP quote
  363. etc.
  364. There is one exception to this rule, and that is if you can "tunnel through"
  365. the given HTTP proxy. Proxy tunneling is enabled with a special option (-p)
  366. and is generally not available as proxy admins usually disable tunneling to
  367. other ports than 443 (which is used for HTTPS access through proxies).
  368. 3.13 Why does my single/double quotes fail?
  369. To specify a command line option that includes spaces, you might need to
  370. put the entire option within quotes. Like in:
  371. curl -d " with spaces " url.com
  372. or perhaps
  373. curl -d ' with spaces ' url.com
  374. Exactly what kind of quotes and how to do this is entirely up to the shell
  375. or command line interpreter that you are using. For most unix shells, you
  376. can more or less pick either single (') or double (") quotes. For
  377. Windows/DOS prompts I believe you're forced to use double (") quotes.
  378. Please study the documentation for your particular environment. Examples in
  379. the curl docs will use a mix of both these ones as shown above. You must
  380. adjust them to work in your environment.
  381. Remember that curl works and runs on more operating systems than most single
  382. individuals have ever tried.
  383. 3.14 Does curl support javascript or pac (automated proxy config)?
  384. Many web pages do magic stuff using embedded javascript. Curl and libcurl
  385. have no built-in support for that, so it will be treated just like any other
  386. contents.
  387. .pac files are a netscape invention and are sometimes used by organizations
  388. to allow them to differentiate which proxies to use. The .pac contents is
  389. just a javascript program that gets invoked by the browser and that returns
  390. the name of the proxy to connect to. Since curl doesn't support javascript,
  391. it can't support .pac proxy configuration either.
  392. Some work-arounds usually suggested to overcome this javascript dependency:
  393. - Depending on the javascript complexity, write up a script that
  394. translates it to another language and execute that.
  395. - Read the javascript code and rewrite the same logic in another language.
  396. - Implement a javascript interpreter, people have successfully used the
  397. Mozilla javascript engine in the past.
  398. - Ask your admins to stop this, for a static proxy setup or similar.
  399. 3.15 Can I do recursive fetches with curl?
  400. No. curl itself has no code that performs recursive operations, such as
  401. those performed by wget and similar tools.
  402. There exist wrapper scripts with that functionality (for example the
  403. curlmirror perl script), and you can write programs based on libcurl to do
  404. it, but the command line tool curl itself cannot.
  405. 3.16 What certificates do I need when I use SSL?
  406. There are three different kinds of "certificates" to keep track of when we
  407. talk about using SSL-based protocols (HTTPS or FTPS) using curl or libcurl.
  408. - Client certificate. The server you communicate may require that you can
  409. provide this in order to prove that you actually are who you claim to be.
  410. If the server doesn't require this, you don't need a client certificate.
  411. - Server certificate. The server you communicate with has a server
  412. certificate. You can and should verify this certificate to make sure that
  413. you are truly talking to the real server and not a server impersonating
  414. it.
  415. - Certificate Authority certificate ("CA cert"). You often have several CA
  416. certs in a CA cert bundle that can be used to verify a server certificate
  417. that was signed by one of the authorities in the bundle. curl comes with a
  418. default CA cert bundle. You can override the default.
  419. The server certificate verification process is made by using a Certificate
  420. Authority certificate ("CA cert") that was used to sign the server
  421. certificate. Server certificate verification is enabled by default in curl
  422. and libcurl and is often the reason for problems as explained in FAQ entry
  423. 4.12 and the SSLCERTS document
  424. (http://curl.haxx.se/docs/sslcerts.html). Server certificates that are
  425. "self-signed" or otherwise signed by a CA that you do not have a CA cert
  426. for, cannot be verified. If the verification during a connect fails, you
  427. are refused access. You then need to explicitly disable the verification
  428. to connect to the server.
  429. 3.17 How do I list the root dir of an FTP server?
  430. There are two ways. The way defined in the RFC is to use an encoded slash
  431. in the first path part. List the "/tmp" dir like this:
  432. curl ftp://ftp.sunet.se/%2ftmp/
  433. or the not-quite-kosher-but-more-readable way, by simply starting the path
  434. section of the URL with a slash:
  435. curl ftp://ftp.sunet.se//tmp/
  436. 3.18 Can I use curl to send a POST/PUT and not wait for a response?
  437. No.
  438. But you could easily write your own program using libcurl to do such stunts.
  439. 4. Running Problems
  440. 4.1 Problems connecting to SSL servers.
  441. It took a very long time before we could sort out why curl had problems to
  442. connect to certain SSL servers when using SSLeay or OpenSSL v0.9+. The
  443. error sometimes showed up similar to:
  444. 16570:error:1407D071:SSL routines:SSL2_READ:bad mac decode:s2_pkt.c:233:
  445. It turned out to be because many older SSL servers don't deal with SSLv3
  446. requests properly. To correct this problem, tell curl to select SSLv2 from
  447. the command line (-2/--sslv2).
  448. There have also been examples where the remote server didn't like the SSLv2
  449. request and instead you had to force curl to use SSLv3 with -3/--sslv3.
  450. 4.2 Why do I get problems when I use & or % in the URL?
  451. In general unix shells, the & letter is treated special and when used, it
  452. runs the specified command in the background. To safely send the & as a part
  453. of a URL, you should quote the entire URL by using single (') or double (")
  454. quotes around it.
  455. An example that would invoke a remote CGI that uses &-letters could be:
  456. curl 'http://www.altavista.com/cgi-bin/query?text=yes&q=curl'
  457. In Windows, the standard DOS shell treats the %-letter specially and you
  458. need to use TWO %-letters for each single one you want to use in the URL.
  459. Also note that if you want the literal %-letter to be part of the data you
  460. pass in a POST using -d/--data you must encode it as '%25' (which then also
  461. needs the %-letter doubled on Windows machines).
  462. 4.3 How can I use {, }, [ or ] to specify multiple URLs?
  463. Because those letters have a special meaning to the shell, and to be used in
  464. a URL specified to curl you must quote them.
  465. An example that downloads two URLs (sequentially) would do:
  466. curl '{curl,www}.haxx.se'
  467. To be able to use those letters as actual parts of the URL (without using
  468. them for the curl URL "globbing" system), use the -g/--globoff option:
  469. curl -g 'www.site.com/weirdname[].html'
  470. 4.4 Why do I get downloaded data even though the web page doesn't exist?
  471. Curl asks remote servers for the page you specify. If the page doesn't exist
  472. at the server, the HTTP protocol defines how the server should respond and
  473. that means that headers and a "page" will be returned. That's simply how
  474. HTTP works.
  475. By using the --fail option you can tell curl explicitly to not get any data
  476. if the HTTP return code doesn't say success.
  477. 4.5 Why do I get return code XXX from a HTTP server?
  478. RFC2616 clearly explains the return codes. This is a short transcript. Go
  479. read the RFC for exact details:
  480. 4.5.1 "400 Bad Request"
  481. The request could not be understood by the server due to malformed
  482. syntax. The client SHOULD NOT repeat the request without modifications.
  483. 4.5.2 "401 Unauthorized"
  484. The request requires user authentication.
  485. 4.5.3 "403 Forbidden"
  486. The server understood the request, but is refusing to fulfill it.
  487. Authorization will not help and the request SHOULD NOT be repeated.
  488. 4.5.4 "404 Not Found"
  489. The server has not found anything matching the Request-URI. No indication
  490. is given of whether the condition is temporary or permanent.
  491. 4.5.5 "405 Method Not Allowed"
  492. The method specified in the Request-Line is not allowed for the resource
  493. identified by the Request-URI. The response MUST include an Allow header
  494. containing a list of valid methods for the requested resource.
  495. 4.5.6 "301 Moved Permanently"
  496. If you get this return code and an HTML output similar to this:
  497. <H1>Moved Permanently</H1> The document has moved <A
  498. HREF="http://same_url_now_with_a_trailing_slash/">here</A>.
  499. it might be because you request a directory URL but without the trailing
  500. slash. Try the same operation again _with_ the trailing URL, or use the
  501. -L/--location option to follow the redirection.
  502. 4.6 Can you tell me what error code 142 means?
  503. All curl error codes are described at the end of the man page, in the
  504. section called "EXIT CODES".
  505. Error codes that are larger than the highest documented error code means
  506. that curl has exited due to a crash. This is a serious error, and we
  507. appreciate a detailed bug report from you that describes how we could go
  508. ahead and repeat this!
  509. 4.7 How do I keep user names and passwords secret in Curl command lines?
  510. This problem has two sides:
  511. The first part is to avoid having clear-text passwords in the command line
  512. so that they don't appear in 'ps' outputs and similar. That is easily
  513. avoided by using the "-K" option to tell curl to read parameters from a file
  514. or stdin to which you can pass the secret info. curl itself will also
  515. attempt to "hide" the given password by blanking out the option - this
  516. doesn't work on all platforms.
  517. To keep the passwords in your account secret from the rest of the world is
  518. not a task that curl addresses. You could of course encrypt them somehow to
  519. at least hide them from being read by human eyes, but that is not what
  520. anyone would call security.
  521. Also note that regular HTTP (using Basic authentication) and FTP passwords
  522. are sent in clear across the network. All it takes for anyone to fetch them
  523. is to listen on the network. Eavesdropping is very easy. Use more secure
  524. authentication methods (like Digest, Negotiate or even NTLM) or consider the
  525. SSL-based alternatives HTTPS and FTPS.
  526. 4.8 I found a bug!
  527. It is not a bug if the behavior is documented. Read the docs first.
  528. Especially check out the KNOWN_BUGS file, it may be a documented bug!
  529. If it is a problem with a binary you've downloaded or a package for your
  530. particular platform, try contacting the person who built the package/archive
  531. you have.
  532. If there is a bug, read the BUGS document first. Then report it as described
  533. in there.
  534. 4.9 Curl can't authenticate to the server that requires NTLM?
  535. This is supported in curl 7.10.6 or later. No earlier curl version knows
  536. of this magic.
  537. NTLM is a Microsoft proprietary protocol. Proprietary formats are evil. You
  538. should not use such ones.
  539. 4.10 My HTTP request using HEAD, PUT or DELETE doesn't work!
  540. Many web servers allow or demand that the administrator configures the
  541. server properly for these requests to work on the web server.
  542. Some servers seem to support HEAD only on certain kinds of URLs.
  543. To fully grasp this, try the documentation for the particular server
  544. software you're trying to interact with. This is not anything curl can do
  545. anything about.
  546. 4.11 Why does my HTTP range requests return the full document?
  547. Because the range may not be supported by the server, or the server may
  548. choose to ignore it and return the full document anyway.
  549. 4.12 Why do I get "certificate verify failed" ?
  550. You invoke curl 7.10 or later to communicate on a https:// URL and get an
  551. error back looking something similar to this:
  552. curl: (35) SSL: error:14090086:SSL routines:
  553. SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
  554. Then it means that curl couldn't verify that the server's certificate was
  555. good. Curl verifies the certificate using the CA cert bundle that comes with
  556. the curl installation.
  557. To disable the verification (which makes it act like curl did before 7.10),
  558. use -k. This does however enable man-in-the-middle attacks.
  559. If you get this failure but are having a CA cert bundle installed and used,
  560. the server's certificate is not signed by one of the CA's in the bundle. It
  561. might for example be self-signed. You then correct this problem by obtaining
  562. a valid CA cert for the server. Or again, decrease the security by disabling
  563. this check.
  564. Details are also in the SSLCERTS file in the release archives, found online
  565. here: http://curl.haxx.se/docs/sslcerts.html
  566. 4.13 Why is curl -R on Windows one hour off?
  567. During daylight savings time, when -R is used, curl will set a time that
  568. appears one hour off. This happens due to a flaw in how Windows stores and
  569. uses file modification times and it is not easily worked around. For details
  570. on this problem, read this: http://www.codeproject.com/datetime/dstbugs.asp
  571. 4.14 Redirects work in browser but not with curl!
  572. curl supports HTTP redirects fine (see item 3.8). Browsers generally support
  573. at least two other ways to perform directs that curl does not:
  574. - Meta tags. You can write a HTML tag that will cause the browser to
  575. redirect to another given URL after a certain time.
  576. - Javascript. You can write a javascript program embeded in a HTML page
  577. that redirects the browser to another given URL.
  578. There is no way to make curl follow these redirects. You must either
  579. manually figure out what the page is set to do, or you write a script that
  580. parses the results and fetches the new URL.
  581. 5. libcurl Issues
  582. 5.1 Is libcurl thread-safe?
  583. Yes.
  584. We have written the libcurl code specifically adjusted for multi-threaded
  585. programs. libcurl will use thread-safe functions instead of non-safe ones if
  586. your system has such.
  587. If you use a OpenSSL-powered libcurl in a multi-threaded environment, you
  588. need to provide one or two locking functions:
  589. http://www.openssl.org/docs/crypto/threads.html#DESCRIPTION
  590. If you use a GnuTLS-powered libcurl in a multi-threaded environment, you
  591. need to provide locking function(s) for libgcrypt (which is used by GnuTLS
  592. for the crypto functions).
  593. http://www.gnu.org/software/gnutls/manual/html_node/Multi_002dthreaded-applications.html
  594. 5.2 How can I receive all data into a large memory chunk?
  595. [ See also the examples/getinmemory.c source ]
  596. You are in full control of the callback function that gets called every time
  597. there is data received from the remote server. You can make that callback do
  598. whatever you want. You do not have to write the received data to a file.
  599. One solution to this problem could be to have a pointer to a struct that you
  600. pass to the callback function. You set the pointer using the
  601. CURLOPT_WRITEDATA option. Then that pointer will be passed to the callback
  602. instead of a FILE * to a file:
  603. /* imaginary struct */
  604. struct MemoryStruct {
  605. char *memory;
  606. size_t size;
  607. };
  608. /* imaginary callback function */
  609. size_t
  610. WriteMemoryCallback(void *ptr, size_t size, size_t nmemb, void *data)
  611. {
  612. size_t realsize = size * nmemb;
  613. struct MemoryStruct *mem = (struct MemoryStruct *)data;
  614. mem->memory = (char *)realloc(mem->memory, mem->size + realsize + 1);
  615. if (mem->memory) {
  616. memcpy(&(mem->memory[mem->size]), ptr, realsize);
  617. mem->size += realsize;
  618. mem->memory[mem->size] = 0;
  619. }
  620. return realsize;
  621. }
  622. 5.3 How do I fetch multiple files with libcurl?
  623. libcurl has excellent support for transferring multiple files. You should
  624. just repeatedly set new URLs with curl_easy_setopt() and then transfer it
  625. with curl_easy_perform(). The handle you get from curl_easy_init() is not
  626. only reusable, but you're even encouraged to reuse it if you can, as that
  627. will enable libcurl to use persistent connections.
  628. 5.4 Does libcurl do Winsock initialization on win32 systems?
  629. Yes, if told to in the curl_global_init() call.
  630. 5.5 Does CURLOPT_WRITEDATA and CURLOPT_READDATA work on win32 ?
  631. Yes, but you cannot open a FILE * and pass the pointer to a DLL and have
  632. that DLL use the FILE * (as the DLL and the client application cannot access
  633. each others' variable memory areas). If you set CURLOPT_WRITEDATA you must
  634. also use CURLOPT_WRITEFUNCTION as well to set a function that writes the
  635. file, even if that simply writes the data to the specified FILE *.
  636. Similarly, if you use CURLOPT_READDATA you must also specify
  637. CURLOPT_READFUNCTION.
  638. (Provided by Joel DeYoung and Bob Schader)
  639. 5.6 What about Keep-Alive or persistent connections?
  640. curl and libcurl have excellent support for persistent connections when
  641. transferring several files from the same server. Curl will attempt to reuse
  642. connections for all URLs specified on the same command line/config file, and
  643. libcurl will reuse connections for all transfers that are made using the
  644. same libcurl handle.
  645. 5.7 Link errors when building libcurl on Windows!
  646. You need to make sure that your project, and all the libraries (both static
  647. and dynamic) that it links against, are compiled/linked against the same run
  648. time library.
  649. This is determined by the /MD, /ML, /MT (and their corresponding /M?d)
  650. options to the command line compiler. /MD (linking against MSVCRT dll) seems
  651. to be the most commonly used option.
  652. (Provided by Andrew Francis)
  653. When building an application that uses the static libcurl library, you must
  654. add -DCURL_STATICLIB to your CFLAGS. Otherwise the linker will look for
  655. dynamic import symbols. If you get linker error like "unknown symbol
  656. __imp__curl_easy_init ..." you have linked against the wrong (static)
  657. library. If you want to use the libcurl.dll and import lib, you don't need
  658. any extra CFLAGS, but use one of the import libraries below. These are the
  659. libraries produced by the various lib/Makefile.* files:
  660. Target: static lib. import lib for libcurl*.dll.
  661. -----------------------------------------------------------
  662. MingW: libcurl.a libcurldll.a
  663. MSVC (release): libcurl.lib libcurl_imp.lib
  664. MSVC (debug): libcurld.lib libcurld_imp.lib
  665. Borland: libcurl.lib libcurl_imp.lib
  666. 5.8 libcurl.so.3: open failed: No such file or directory
  667. This is an error message you might get when you try to run a program linked
  668. with a shared version of libcurl and your run-time linker (ld.so) couldn't
  669. find the shared library named libcurl.so.3.
  670. You need to make sure that ld.so finds libcurl.so.3. You can do that
  671. multiple ways, and it differs somewhat between different operating systems,
  672. but they are usually:
  673. * Add an option to the linker command line that specify the hard-coded path
  674. the run-time linker should check for the lib (usually -R)
  675. * Set an environment variable (LD_LIBRARY_PATH for example) where ld.so
  676. should check for libs
  677. * Adjust the system's config to check for libs in the directory where you've
  678. put the dir (like Linux's /etc/ld.so.conf)
  679. 'man ld.so' and 'man ld' will tell you more details
  680. 5.9 How does libcurl resolve host names?
  681. libcurl supports a large a number of different name resolve functions. One
  682. of them is picked at build-time and will be used unconditionally. Thus, if
  683. you want to change name resolver function you must rebuild libcurl and tell
  684. it to use a different function.
  685. - The non-ipv6 resolver that can use one out of four host name resolve calls
  686. (depending on what your system supports):
  687. A - gethostbyname()
  688. B - gethostbyname_r() with 3 arguments
  689. C - gethostbyname_r() with 5 arguments
  690. D - gethostbyname_r() with 6 arguments
  691. - The ipv6-resolver that uses getaddrinfo()
  692. - The c-ares based name resolver that uses the c-ares library for resolves.
  693. Using this offers asynchronous name resolves but it currently has no IPv6
  694. support.
  695. - The Windows threaded resolver. It use:
  696. A - gethostbyname() on plain ipv4 windows hosts
  697. B - getaddrinfo() on ipv6-enabled windows hosts
  698. Also note that libcurl never resolves or reverse-lookups addresses given as
  699. pure numbers, such as 127.0.0.1 or ::1.
  700. 5.10 How do I prevent libcurl from writing the response to stdout?
  701. libcurl provides a default built-in write function that writes received data
  702. to stdout. Set the CURLOPT_WRITEFUNCTION to receive the data, or possibly
  703. set CURLOPT_WRITEDATA to a different FILE * handle.
  704. 5.11 How do I make libcurl not receive the whole HTTP response?
  705. You make the write callback (or progress callback) return an error and
  706. libcurl will then abort the transfer.
  707. 5.12 Can I make libcurl fake or hide my real IP address?
  708. No. libcurl operates on a higher level than so. Besides, faking IP address
  709. would imply sending IP packages with a made-up source address, and then you
  710. normally get a problem with intercepting the packages sent back as they
  711. would then not be routed to you!
  712. If you use a proxy to access remote sites, the sites will not see your local
  713. IP address but instead the address of the proxy.
  714. Also note that on many networks NATs or other IP-munging techniques are used
  715. that makes you see and use a different IP address locally than what the
  716. remote server will see you coming from.
  717. 6. License Issues
  718. Curl and libcurl are released under a MIT/X derivate license. The license is
  719. very liberal and should not impose a problem for your project. This section
  720. is just a brief summary for the cases we get the most questions. (Parts of
  721. this section was much enhanced by Bjorn Reese.)
  722. We are not lawyers and this is not legal advice. You should probably consult
  723. one if you want true and accurate legal insights without our prejudice.
  724. 6.1 I have a GPL program, can I use the libcurl library?
  725. Yes!
  726. Since libcurl may be distributed under the MIT/X derivate license, it can be
  727. used together with GPL in any software.
  728. 6.2 I have a closed-source program, can I use the libcurl library?
  729. Yes!
  730. libcurl does not put any restrictions on the program that uses the library.
  731. 6.3 I have a BSD licensed program, can I use the libcurl library?
  732. Yes!
  733. libcurl does not put any restrictions on the program that uses the library.
  734. 6.4 I have a program that uses LGPL libraries, can I use libcurl?
  735. Yes!
  736. The LGPL license doesn't clash with other licenses.
  737. 6.5 Can I modify curl/libcurl for my program and keep the changes secret?
  738. Yes!
  739. The MIT/X derivate license practically allows you to do almost anything with
  740. the sources, on the condition that the copyright texts in the sources are
  741. left intact.
  742. 6.6 Can you please change the curl/libcurl license to XXXX?
  743. No.
  744. We have carefully picked this license after years of development and
  745. discussions and a large amount of people have contributed with source code
  746. knowing that this is the license we use. This license puts the restrictions
  747. we want on curl/libcurl and it does not spread to other programs or
  748. libraries that use it. It should be possible for everyone to use libcurl or
  749. curl in their projects, no matter what license they already have in use.
  750. 6.7 What are my obligations when using libcurl in my commerical apps?
  751. Next to none. All you need to adhere to is the MIT-style license (stated in
  752. the COPYING file) which basically says you have to include the copyright
  753. notice in "all copies" and that you may not use the copyright holder's name
  754. when promoting your software.
  755. You do not have to release any of your source code.
  756. You do not have to reveal or make public any changes to the libcurl source
  757. code.
  758. You do not have to reveal or make public that you are using libcurl within
  759. your app.
  760. As can be seen here: http://curl.haxx.se/docs/companies.html and
  761. elsewhere, more and more companies are dicovering the power
  762. of libcurl and take advantage of it even in commercial environments.
  763. 7. PHP/CURL Issues
  764. 7.1 What is PHP/CURL?
  765. The module for PHP that makes it possible for PHP programs to access curl-
  766. functions from within PHP.
  767. In the cURL project we call this module PHP/CURL to differentiate it from
  768. curl the command line tool and libcurl the library. The PHP team however
  769. does not refer to it like this (for unknown reasons). They call it plain
  770. CURL (often using all caps) which causes much confusion to users which in
  771. turn gives us a higher question load.
  772. 7.2 Who write PHP/CURL?
  773. PHP/CURL is a module that comes with the regular PHP package. It depends and
  774. uses libcurl, so you need to have libcurl installed properly first before
  775. PHP/CURL can be used. PHP/CURL is written by Sterling Hughes.
  776. 7.3 Can I perform multiple requests using the same handle?
  777. Yes - at least in PHP version 4.3.8 and later (this has been known to not
  778. work in earlier versions, but the exact version when it started to work is
  779. unknown to me).
  780. After a transfer, you just set new options in the handle and make another
  781. transfer. This will make libcurl to re-use the same connection if it can.