From ad1b9480f2ef5a4450f8b31ef7b3141ee7462b4f Mon Sep 17 00:00:00 2001 From: "Maxin B. John" Date: Mon, 4 Aug 2014 13:04:44 +0200 Subject: curl: remove unused patch Remove unused "remove_inappropriate_file_from_rel.patch" Signed-off-by: Maxin B. John Signed-off-by: Saul Wold Signed-off-by: Richard Purdie --- .../curl/remove_inappropriate_file_from_rel.patch | 8203 -------------------- 1 file changed, 8203 deletions(-) delete mode 100644 meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch (limited to 'meta/recipes-support/curl') diff --git a/meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch b/meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch deleted file mode 100644 index e4b8fe2ab6..0000000000 --- a/meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch +++ /dev/null @@ -1,8203 +0,0 @@ -Upstream-Status: Backport [to be fixed in 7.37.0] -Signed-off-by: Tudor Florea - -diff -ruN a/src/tool_hugehelp.c b/src/tool_hugehelp.c ---- a/src/tool_hugehelp.c 2014-03-25 11:29:49.000000000 +0100 -+++ b/src/tool_hugehelp.c 1970-01-01 01:00:00.000000000 +0100 -@@ -1,8196 +0,0 @@ --#include "tool_setup.h" --#ifndef HAVE_LIBZ --/* -- * NEVER EVER edit this manually, fix the mkhelp.pl script instead! -- * Generation time: Tue Mar 25 11:29:49 2014 -- */ --#ifdef USE_MANUAL --#include "tool_hugehelp.h" --void hugehelp(void) --{ -- fputs( --" _ _ ____ _\n" --" Project ___| | | | _ \\| |\n" --" / __| | | | |_) | |\n" --" | (__| |_| | _ <| |___\n" --" \\___|\\___/|_| \\_\\_____|\n" --"\n" --"NAME\n" --" curl - transfer a URL\n" --"\n" --"SYNOPSIS\n" --" curl [options] [URL...]\n" --"\n" --"DESCRIPTION\n" --" curl is a tool to transfer data from or to a server, using one of the\n" --" supported protocols (DICT, FILE, FTP, FTPS, GOPHER, HTTP, HTTPS, IMAP,\n" --, stdout); -- fputs( --" IMAPS, LDAP, LDAPS, POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS,\n" --" TELNET and TFTP). The command is designed to work without user inter-\n" --" action.\n" --"\n" --" curl offers a busload of useful tricks like proxy support, user authen-\n" --" tication, FTP upload, HTTP post, SSL connections, cookies, file trans-\n" --" fer resume, Metalink, and more. As you will see below, the number of\n" --" features will make your head spin!\n" --"\n" --, stdout); -- fputs( --" curl is powered by libcurl for all transfer-related features. See\n" --" libcurl(3) for details.\n" --"\n" --"URL\n" --" The URL syntax is protocol-dependent. You'll find a detailed descrip-\n" --" tion in RFC 3986.\n" --"\n" --" You can specify multiple URLs or parts of URLs by writing part sets\n" --" within braces as in:\n" --"\n" --" http://site.{one,two,three}.com\n" --"\n" --" or you can get sequences of alphanumeric series by using [] as in:\n" --"\n" --" ftp://ftp.numericals.com/file[1-100].txt\n" --, stdout); -- fputs( --" ftp://ftp.numericals.com/file[001-100].txt (with leading zeros)\n" --" ftp://ftp.letters.com/file[a-z].txt\n" --"\n" --" Nested sequences are not supported, but you can use several ones next\n" --" to each other:\n" --"\n" --" http://any.org/archive[1996-1999]/vol[1-4]/part{a,b,c}.html\n" --"\n" --" You can specify any amount of URLs on the command line. They will be\n" --" fetched in a sequential manner in the specified order.\n" --"\n" --, stdout); -- fputs( --" You can specify a step counter for the ranges to get every Nth number\n" --" or letter:\n" --"\n" --" http://www.numericals.com/file[1-100:10].txt\n" --" http://www.letters.com/file[a-z:2].txt\n" --"\n" --" If you specify URL without protocol:// prefix, curl will attempt to\n" --" guess what protocol you might want. It will then default to HTTP but\n" --" try other protocols based on often-used host name prefixes. For exam-\n" --, stdout); -- fputs( --" ple, for host names starting with \"ftp.\" curl will assume you want to\n" --" speak FTP.\n" --"\n" --" curl will do its best to use what you pass to it as a URL. It is not\n" --" trying to validate it as a syntactically correct URL by any means but\n" --" is instead very liberal with what it accepts.\n" --"\n" --" curl will attempt to re-use connections for multiple file transfers, so\n" --" that getting many files from the same server will not do multiple con-\n" --, stdout); -- fputs( --" nects / handshakes. This improves speed. Of course this is only done on\n" --" files specified on a single command line and cannot be used between\n" --" separate curl invokes.\n" --"\n" --"PROGRESS METER\n" --" curl normally displays a progress meter during operations, indicating\n" --" the amount of transferred data, transfer speeds and estimated time\n" --" left, etc.\n" --"\n" --" curl displays this data to the terminal by default, so if you invoke\n" --, stdout); -- fputs( --" curl to do an operation and it is about to write data to the terminal,\n" --" it disables the progress meter as otherwise it would mess up the output\n" --" mixing progress meter and response data.\n" --"\n" --" If you want a progress meter for HTTP POST or PUT requests, you need to\n" --" redirect the response output to a file, using shell redirect (>), -o\n" --" [file] or similar.\n" --"\n" --" It is not the same case for FTP upload as that operation does not spit\n" --, stdout); -- fputs( --" out any response data to the terminal.\n" --"\n" --" If you prefer a progress \"bar\" instead of the regular meter, -# is your\n" --" friend.\n" --"OPTIONS\n" --" Options start with one or two dashes. Many of the options require an\n" --" addition value next to it.\n" --"\n" --" The short \"single-dash\" form of the options, -d for example, may be\n" --" used with or without a space between it and its value, although a space\n" --" is a recommended separator. The long \"double-dash\" form, --data for\n" --, stdout); -- fputs( --" example, requires a space between it and its value.\n" --"\n" --" Short version options that don't need any additional values can be used\n" --" immediately next to each other, like for example you can specify all\n" --" the options -O, -L and -v at once as -OLv.\n" --"\n" --" In general, all boolean options are enabled with --option and yet again\n" --" disabled with --no-option. That is, you use the exact same option name\n" --, stdout); -- fputs( --" but prefix it with \"no-\". However, in this list we mostly only list and\n" --" show the --option version of them. (This concept with --no options was\n" --" added in 7.19.0. Previously most options were toggled on/off on\n" --" repeated use of the same command line option.)\n" --"\n" --" -#, --progress-bar\n" --" Make curl display progress as a simple progress bar instead of\n" --" the standard, more informational, meter.\n" --"\n" --" -:, --next\n" --, stdout); -- fputs( --" Tells curl to use a separate operation for the following URL and\n" --" associated options. This allows you to send several URL\n" --" requests, each with their own specific options, for example,\n" --" such as different user names or custom requests for each. (Added\n" --" in 7.36.0)\n" --"\n" --" -0, --http1.0\n" --" (HTTP) Tells curl to use HTTP version 1.0 instead of using its\n" --" internally preferred: HTTP 1.1.\n" --"\n" --, stdout); -- fputs( --" --http1.1\n" --" (HTTP) Tells curl to use HTTP version 1.1. This is the internal\n" --" default version. (Added in 7.33.0)\n" --"\n" --" --http2\n" --" (HTTP) Tells curl to issue its requests using HTTP 2. This\n" --" requires that the underlying libcurl was built to support it.\n" --" (Added in 7.33.0)\n" --"\n" --" --no-npn\n" --" Disable the NPN TLS extension. NPN is enabled by default if\n" --, stdout); -- fputs( --" libcurl was built with an SSL library that supports NPN. NPN is\n" --" used by a libcurl that supports HTTP 2 to negotiate HTTP 2 sup-\n" --" port with the server during https sessions.\n" --"\n" --" (Added in 7.36.0)\n" --"\n" --" --no-alpn\n" --" Disable the ALPN TLS extension. ALPN is enabled by default if\n" --" libcurl was built with an SSL library that supports ALPN. ALPN\n" --, stdout); -- fputs( --" is used by a libcurl that supports HTTP 2 to negotiate HTTP 2\n" --" support with the server during https sessions.\n" --"\n" --" (Added in 7.36.0)\n" --"\n" --" -1, --tlsv1\n" --" (SSL) Forces curl to use TLS version 1.x when negotiating with a\n" --" remote TLS server. You can use options --tlsv1.0, --tlsv1.1,\n" --" and --tlsv1.2 to control the TLS version more precisely (if the\n" --" SSL backend in use supports such a level of control).\n" --"\n" --, stdout); -- fputs( --" -2, --sslv2\n" --" (SSL) Forces curl to use SSL version 2 when negotiating with a\n" --" remote SSL server.\n" --"\n" --" -3, --sslv3\n" --" (SSL) Forces curl to use SSL version 3 when negotiating with a\n" --" remote SSL server.\n" --"\n" --" -4, --ipv4\n" --" If curl is capable of resolving an address to multiple IP ver-\n" --" sions (which it is if it is IPv6-capable), this option tells\n" --" curl to resolve names to IPv4 addresses only.\n" --, stdout); -- fputs( --"\n" --" -6, --ipv6\n" --" If curl is capable of resolving an address to multiple IP ver-\n" --" sions (which it is if it is IPv6-capable), this option tells\n" --" curl to resolve names to IPv6 addresses only.\n" --"\n" --" -a, --append\n" --" (FTP/SFTP) When used in an upload, this will tell curl to append\n" --" to the target file instead of overwriting it. If the file\n" --" doesn't exist, it will be created. Note that this flag is\n" --, stdout); -- fputs( --" ignored by some SSH servers (including OpenSSH).\n" --"\n" --" -A, --user-agent \n" --" (HTTP) Specify the User-Agent string to send to the HTTP server.\n" --" Some badly done CGIs fail if this field isn't set to\n" --" \"Mozilla/4.0\". To encode blanks in the string, surround the\n" --" string with single quote marks. This can also be set with the\n" --" -H, --header option of course.\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" --anyauth\n" --" (HTTP) Tells curl to figure out authentication method by itself,\n" --" and use the most secure one the remote site claims to support.\n" --" This is done by first doing a request and checking the response-\n" --" headers, thus possibly inducing an extra network round-trip.\n" --" This is used instead of setting a specific authentication\n" --, stdout); -- fputs( --" method, which you can do with --basic, --digest, --ntlm, and\n" --" --negotiate.\n" --"\n" --" Note that using --anyauth is not recommended if you do uploads\n" --" from stdin, since it may require data to be sent twice and then\n" --" the client must be able to rewind. If the need should arise when\n" --" uploading from stdin, the upload operation will fail.\n" --"\n" --" -b, --cookie \n" --, stdout); -- fputs( --" (HTTP) Pass the data to the HTTP server as a cookie. It is sup-\n" --" posedly the data previously received from the server in a \"Set-\n" --" Cookie:\" line. The data should be in the format \"NAME1=VALUE1;\n" --" NAME2=VALUE2\".\n" --"\n" --" If no '=' symbol is used in the line, it is treated as a file-\n" --" name to use to read previously stored cookie lines from, which\n" --, stdout); -- fputs( --" should be used in this session if they match. Using this method\n" --" also activates the \"cookie parser\" which will make curl record\n" --" incoming cookies too, which may be handy if you're using this in\n" --" combination with the -L, --location option. The file format of\n" --" the file to read cookies from should be plain HTTP headers or\n" --" the Netscape/Mozilla cookie file format.\n" --"\n" --, stdout); -- fputs( --" NOTE that the file specified with -b, --cookie is only used as\n" --" input. No cookies will be stored in the file. To store cookies,\n" --" use the -c, --cookie-jar option or you could even save the HTTP\n" --" headers to a file using -D, --dump-header!\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -B, --use-ascii\n" --" (FTP/LDAP) Enable ASCII transfer. For FTP, this can also be\n" --, stdout); -- fputs( --" enforced by using an URL that ends with \";type=A\". This option\n" --" causes data sent to stdout to be in text mode for win32 systems.\n" --"\n" --" --basic\n" --" (HTTP) Tells curl to use HTTP Basic authentication. This is the\n" --" default and this option is usually pointless, unless you use it\n" --" to override a previously set option that sets a different\n" --" authentication method (such as --ntlm, --digest, or --negoti-\n" --, stdout); -- fputs( --" ate).\n" --"\n" --" -c, --cookie-jar \n" --" (HTTP) Specify to which file you want curl to write all cookies\n" --" after a completed operation. Curl writes all cookies previously\n" --" read from a specified file as well as all cookies received from\n" --" remote server(s). If no cookies are known, no file will be writ-\n" --" ten. The file will be written using the Netscape cookie file\n" --, stdout); -- fputs( --" format. If you set the file name to a single dash, \"-\", the\n" --" cookies will be written to stdout.\n" --"\n" --" This command line option will activate the cookie engine that\n" --" makes curl record and use cookies. Another way to activate it is\n" --" to use the -b, --cookie option.\n" --"\n" --" If the cookie jar can't be created or written to, the whole curl\n" --" operation won't fail or even report an error clearly. Using -v\n" --, stdout); -- fputs( --" will get a warning displayed, but that is the only visible feed-\n" --" back you get about this possibly lethal situation.\n" --"\n" --" If this option is used several times, the last specified file\n" --" name will be used.\n" --"\n" --" -C, --continue-at \n" --" Continue/Resume a previous file transfer at the given offset.\n" --" The given offset is the exact number of bytes that will be\n" --, stdout); -- fputs( --" skipped, counting from the beginning of the source file before\n" --" it is transferred to the destination. If used with uploads, the\n" --" FTP server command SIZE will not be used by curl.\n" --"\n" --" Use \"-C -\" to tell curl to automatically find out where/how to\n" --" resume the transfer. It then uses the given output/input files\n" --" to figure that out.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --, stdout); -- fputs( --" --ciphers \n" --" (SSL) Specifies which ciphers to use in the connection. The list\n" --" of ciphers must specify valid ciphers. Read up on SSL cipher\n" --" list details on this URL:\n" --" http://www.openssl.org/docs/apps/ciphers.html\n" --"\n" --" NSS ciphers are done differently than OpenSSL and GnuTLS. The\n" --" full list of NSS ciphers is in the NSSCipherSuite entry at this\n" --, stdout); -- fputs( --" URL: http://git.fedora-\n" --" hosted.org/cgit/mod_nss.git/plain/docs/mod_nss.html#Directives\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --compressed\n" --" (HTTP) Request a compressed response using one of the algorithms\n" --" curl supports, and save the uncompressed document. If this\n" --" option is used and the server sends an unsupported encoding,\n" --, stdout); -- fputs( --" curl will report an error.\n" --"\n" --" --connect-timeout \n" --" Maximum time in seconds that you allow the connection to the\n" --" server to take. This only limits the connection phase, once\n" --" curl has connected this option is of no more use. Since 7.32.0,\n" --" this option accepts decimal values, but the actual timeout will\n" --" decrease in accuracy as the specified timeout increases in deci-\n" --, stdout); -- fputs( --" mal precision. See also the -m, --max-time option.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --create-dirs\n" --" When used in conjunction with the -o option, curl will create\n" --" the necessary local directory hierarchy as needed. This option\n" --" creates the dirs mentioned with the -o option, nothing else. If\n" --" the -o file name uses no dir or if the dirs it mentions already\n" --, stdout); -- fputs( --" exist, no dir will be created.\n" --"\n" --" To create remote directories when using FTP or SFTP, try --ftp-\n" --" create-dirs.\n" --"\n" --" --crlf (FTP) Convert LF to CRLF in upload. Useful for MVS (OS/390).\n" --"\n" --" --crlfile \n" --" (HTTPS/FTPS) Provide a file using PEM format with a Certificate\n" --" Revocation List that may specify peer certificates that are to\n" --" be considered revoked.\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" (Added in 7.19.7)\n" --" -d, --data \n" --" (HTTP) Sends the specified data in a POST request to the HTTP\n" --" server, in the same way that a browser does when a user has\n" --" filled in an HTML form and presses the submit button. This will\n" --" cause curl to pass the data to the server using the content-type\n" --, stdout); -- fputs( --" application/x-www-form-urlencoded. Compare to -F, --form.\n" --"\n" --" -d, --data is the same as --data-ascii. To post data purely\n" --" binary, you should instead use the --data-binary option. To URL-\n" --" encode the value of a form field you may use --data-urlencode.\n" --"\n" --" If any of these options is used more than once on the same com-\n" --" mand line, the data pieces specified will be merged together\n" --, stdout); -- fputs( --" with a separating &-symbol. Thus, using '-d name=daniel -d\n" --" skill=lousy' would generate a post chunk that looks like\n" --" 'name=daniel&skill=lousy'.\n" --"\n" --" If you start the data with the letter @, the rest should be a\n" --" file name to read the data from, or - if you want curl to read\n" --" the data from stdin. Multiple files can also be specified. Post-\n" --, stdout); -- fputs( --" ing data from a file named 'foobar' would thus be done with\n" --" --data @foobar. When --data is told to read from a file like\n" --" that, carriage returns and newlines will be stripped out.\n" --"\n" --" -D, --dump-header \n" --" Write the protocol headers to the specified file.\n" --"\n" --" This option is handy to use when you want to store the headers\n" --" that an HTTP site sends to you. Cookies from the headers could\n" --, stdout); -- fputs( --" then be read in a second curl invocation by using the -b,\n" --" --cookie option! The -c, --cookie-jar option is however a better\n" --" way to store cookies.\n" --"\n" --" When used in FTP, the FTP server response lines are considered\n" --" being \"headers\" and thus are saved there.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --data-ascii \n" --" See -d, --data.\n" --"\n" --" --data-binary \n" --, stdout); -- fputs( --" (HTTP) This posts data exactly as specified with no extra pro-\n" --" cessing whatsoever.\n" --"\n" --" If you start the data with the letter @, the rest should be a\n" --" filename. Data is posted in a similar manner as --data-ascii\n" --" does, except that newlines and carriage returns are preserved\n" --" and conversions are never done.\n" --"\n" --" If this option is used several times, the ones following the\n" --, stdout); -- fputs( --" first will append data as described in -d, --data.\n" --"\n" --" --data-urlencode \n" --" (HTTP) This posts data, similar to the other --data options with\n" --" the exception that this performs URL-encoding. (Added in 7.18.0)\n" --" To be CGI-compliant, the part should begin with a name\n" --" followed by a separator and a content specification. The \n" --" part can be passed to curl using one of the following syntaxes:\n" --"\n" --, stdout); -- fputs( --" content\n" --" This will make curl URL-encode the content and pass that\n" --" on. Just be careful so that the content doesn't contain\n" --" any = or @ symbols, as that will then make the syntax\n" --" match one of the other cases below!\n" --"\n" --" =content\n" --" This will make curl URL-encode the content and pass that\n" --" on. The preceding = symbol is not included in the data.\n" --"\n" --, stdout); -- fputs( --" name=content\n" --" This will make curl URL-encode the content part and pass\n" --" that on. Note that the name part is expected to be URL-\n" --" encoded already.\n" --"\n" --" @filename\n" --" This will make curl load data from the given file\n" --" (including any newlines), URL-encode that data and pass\n" --" it on in the POST.\n" --"\n" --" name@filename\n" --, stdout); -- fputs( --" This will make curl load data from the given file\n" --" (including any newlines), URL-encode that data and pass\n" --" it on in the POST. The name part gets an equal sign\n" --" appended, resulting in name=urlencoded-file-content. Note\n" --" that the name is expected to be URL-encoded already.\n" --"\n" --" --delegation LEVEL\n" --" Set LEVEL to tell the server what it is allowed to delegate when\n" --, stdout); -- fputs( --" it comes to user credentials. Used with GSS/kerberos.\n" --"\n" --" none Don't allow any delegation.\n" --"\n" --" policy Delegates if and only if the OK-AS-DELEGATE flag is set\n" --" in the Kerberos service ticket, which is a matter of\n" --" realm policy.\n" --"\n" --" always Unconditionally allow the server to delegate.\n" --"\n" --" --digest\n" --" (HTTP) Enables HTTP Digest authentication. This is an authenti-\n" --, stdout); -- fputs( --" cation scheme that prevents the password from being sent over\n" --" the wire in clear text. Use this in combination with the normal\n" --" -u, --user option to set user name and password. See also\n" --" --ntlm, --negotiate and --anyauth for related options.\n" --"\n" --" If this option is used several times, only the first one is\n" --" used.\n" --"\n" --" --disable-eprt\n" --, stdout); -- fputs( --" (FTP) Tell curl to disable the use of the EPRT and LPRT commands\n" --" when doing active FTP transfers. Curl will normally always first\n" --" attempt to use EPRT, then LPRT before using PORT, but with this\n" --" option, it will use PORT right away. EPRT and LPRT are exten-\n" --" sions to the original FTP protocol, and may not work on all\n" --" servers, but they enable more functionality in a better way than\n" --, stdout); -- fputs( --" the traditional PORT command.\n" --"\n" --" --eprt can be used to explicitly enable EPRT again and --no-eprt\n" --" is an alias for --disable-eprt.\n" --"\n" --" Disabling EPRT only changes the active behavior. If you want to\n" --" switch to passive mode you need to not use -P, --ftp-port or\n" --" force it with --ftp-pasv.\n" --"\n" --" --disable-epsv\n" --" (FTP) Tell curl to disable the use of the EPSV command when\n" --, stdout); -- fputs( --" doing passive FTP transfers. Curl will normally always first\n" --" attempt to use EPSV before PASV, but with this option, it will\n" --" not try using EPSV.\n" --"\n" --" --epsv can be used to explicitly enable EPSV again and --no-epsv\n" --" is an alias for --disable-epsv.\n" --"\n" --" Disabling EPSV only changes the passive behavior. If you want to\n" --" switch to active mode you need to use -P, --ftp-port.\n" --"\n" --, stdout); -- fputs( --" --dns-interface \n" --" Tell curl to send outgoing DNS requests through .\n" --" This option is a counterpart to --interface (which does not\n" --" affect DNS). The supplied string must be an interface name (not\n" --" an address).\n" --"\n" --" This option requires that libcurl was built with a resolver\n" --" backend that supports this operation. The c-ares backend is the\n" --, stdout); -- fputs( --" only such one. (Added in 7.33.0)\n" --"\n" --" --dns-ipv4-addr \n" --" Tell curl to bind to when making IPv4 DNS requests,\n" --" so that the DNS requests originate from this address. The argu-\n" --" ment should be a single IPv4 address.\n" --"\n" --" This option requires that libcurl was built with a resolver\n" --" backend that supports this operation. The c-ares backend is the\n" --, stdout); -- fputs( --" only such one. (Added in 7.33.0)\n" --"\n" --" --dns-ipv6-addr \n" --" Tell curl to bind to when making IPv6 DNS requests,\n" --" so that the DNS requests originate from this address. The argu-\n" --" ment should be a single IPv6 address.\n" --"\n" --" This option requires that libcurl was built with a resolver\n" --" backend that supports this operation. The c-ares backend is the\n" --, stdout); -- fputs( --" only such one. (Added in 7.33.0)\n" --"\n" --" --dns-servers \n" --" Set the list of DNS servers to be used instead of the system\n" --" default. The list of IP addresses should be separated with com-\n" --" mas. Port numbers may also optionally be given as :\n" --" after each IP address.\n" --"\n" --" This option requires that libcurl was built with a resolver\n" --, stdout); -- fputs( --" backend that supports this operation. The c-ares backend is the\n" --" only such one. (Added in 7.33.0)\n" --"\n" --" -e, --referer \n" --" (HTTP) Sends the \"Referrer Page\" information to the HTTP server.\n" --" This can also be set with the -H, --header flag of course. When\n" --" used with -L, --location you can append \";auto\" to the --referer\n" --" URL to make curl automatically set the previous URL when it fol-\n" --, stdout); -- fputs( --" lows a Location: header. The \";auto\" string can be used alone,\n" --" even if you don't set an initial --referer.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -E, --cert \n" --" (SSL) Tells curl to use the specified client certificate file\n" --" when getting a file with HTTPS, FTPS or another SSL-based proto-\n" --" col. The certificate must be in PKCS#12 format if using Secure\n" --, stdout); -- fputs( --" Transport, or PEM format if using any other engine. If the\n" --" optional password isn't specified, it will be queried for on the\n" --" terminal. Note that this option assumes a \"certificate\" file\n" --" that is the private key and the private certificate concate-\n" --" nated! See --cert and --key to specify them independently.\n" --"\n" --" If curl is built against the NSS SSL library then this option\n" --, stdout); -- fputs( --" can tell curl the nickname of the certificate to use within the\n" --" NSS database defined by the environment variable SSL_DIR (or by\n" --" default /etc/pki/nssdb). If the NSS PEM PKCS#11 module (lib-\n" --" nsspem.so) is available then PEM files may be loaded. If you\n" --" want to use a file from the current directory, please precede it\n" --" with \"./\" prefix, in order to avoid confusion with a nickname.\n" --, stdout); -- fputs( --" If the nickname contains \":\", it needs to be preceded by \"\\\" so\n" --" that it is not recognized as password delimiter. If the nick-\n" --" name contains \"\\\", it needs to be escaped as \"\\\\\" so that it is\n" --" not recognized as an escape character.\n" --"\n" --" (iOS and Mac OS X only) If curl is built against Secure Trans-\n" --" port, then the certificate string can either be the name of a\n" --, stdout); -- fputs( --" certificate/private key in the system or user keychain, or the\n" --" path to a PKCS#12-encoded certificate and private key. If you\n" --" want to use a file from the current directory, please precede it\n" --" with \"./\" prefix, in order to avoid confusion with a nickname.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --engine \n" --" Select the OpenSSL crypto engine to use for cipher operations.\n" --, stdout); -- fputs( --" Use --engine list to print a list of build-time supported\n" --" engines. Note that not all (or none) of the engines may be\n" --" available at run-time.\n" --"\n" --" --environment\n" --" (RISC OS ONLY) Sets a range of environment variables, using the\n" --" names the -w option supports, to allow easier extraction of use-\n" --" ful information after having run curl.\n" --"\n" --" --egd-file \n" --, stdout); -- fputs( --" (SSL) Specify the path name to the Entropy Gathering Daemon\n" --" socket. The socket is used to seed the random engine for SSL\n" --" connections. See also the --random-file option.\n" --"\n" --" --cert-type \n" --" (SSL) Tells curl what certificate type the provided certificate\n" --" is in. PEM, DER and ENG are recognized types. If not specified,\n" --" PEM is assumed.\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" --cacert \n" --" (SSL) Tells curl to use the specified certificate file to verify\n" --" the peer. The file may contain multiple CA certificates. The\n" --" certificate(s) must be in PEM format. Normally curl is built to\n" --" use a default file for this, so this option is typically used to\n" --" alter that default file.\n" --"\n" --, stdout); -- fputs( --" curl recognizes the environment variable named 'CURL_CA_BUNDLE'\n" --" if it is set, and uses the given path as a path to a CA cert\n" --" bundle. This option overrides that variable.\n" --"\n" --" The windows version of curl will automatically look for a CA\n" --" certs file named 'curl-ca-bundle.crt', either in the same direc-\n" --" tory as curl.exe, or in the Current Working Directory, or in any\n" --" folder along your PATH.\n" --"\n" --, stdout); -- fputs( --" If curl is built against the NSS SSL library, the NSS PEM\n" --" PKCS#11 module (libnsspem.so) needs to be available for this\n" --" option to work properly.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --capath \n" --" (SSL) Tells curl to use the specified certificate directory to\n" --" verify the peer. Multiple paths can be provided by separating\n" --, stdout); -- fputs( --" them with \":\" (e.g. \"path1:path2:path3\"). The certificates must\n" --" be in PEM format, and if curl is built against OpenSSL, the\n" --" directory must have been processed using the c_rehash utility\n" --" supplied with OpenSSL. Using --capath can allow OpenSSL-powered\n" --" curl to make SSL-connections much more efficiently than using\n" --" --cacert if the --cacert file contains many CA certificates.\n" --"\n" --, stdout); -- fputs( --" If this option is set, the default capath value will be ignored,\n" --" and if it is used several times, the last one will be used.\n" --"\n" --" -f, --fail\n" --" (HTTP) Fail silently (no output at all) on server errors. This\n" --" is mostly done to better enable scripts etc to better deal with\n" --" failed attempts. In normal cases when an HTTP server fails to\n" --" deliver a document, it returns an HTML document stating so\n" --, stdout); -- fputs( --" (which often also describes why and more). This flag will pre-\n" --" vent curl from outputting that and return error 22.\n" --"\n" --" This method is not fail-safe and there are occasions where non-\n" --" successful response codes will slip through, especially when\n" --" authentication is involved (response codes 401 and 407).\n" --"\n" --" -F, --form \n" --" (HTTP) This lets curl emulate a filled-in form in which a user\n" --, stdout); -- fputs( --" has pressed the submit button. This causes curl to POST data\n" --" using the Content-Type multipart/form-data according to RFC\n" --" 2388. This enables uploading of binary files etc. To force the\n" --" 'content' part to be a file, prefix the file name with an @\n" --" sign. To just get the content part from a file, prefix the file\n" --" name with the symbol <. The difference between @ and < is then\n" --, stdout); -- fputs( --" that @ makes a file get attached in the post as a file upload,\n" --" while the < makes a text field and just get the contents for\n" --" that text field from a file.\n" --"\n" --" Example, to send your password file to the server, where 'pass-\n" --" word' is the name of the form-field to which /etc/passwd will be\n" --" the input:\n" --"\n" --" curl -F password=@/etc/passwd www.mypasswords.com\n" --"\n" --, stdout); -- fputs( --" To read content from stdin instead of a file, use - as the file-\n" --" name. This goes for both @ and < constructs.\n" --"\n" --" You can also tell curl what Content-Type to use by using\n" --" 'type=', in a manner similar to:\n" --"\n" --" curl -F \"web=@index.html;type=text/html\" url.com\n" --"\n" --" or\n" --"\n" --" curl -F \"name=daniel;type=text/foo\" url.com\n" --"\n" --" You can also explicitly change the name field of a file upload\n" --, stdout); -- fputs( --" part by setting filename=, like this:\n" --"\n" --" curl -F \"file=@localfile;filename=nameinpost\" url.com\n" --"\n" --" If filename/path contains ',' or ';', it must be quoted by dou-\n" --" ble-quotes like:\n" --"\n" --" curl -F \"file=@\\\"localfile\\\";filename=\\\"nameinpost\\\"\" url.com\n" --"\n" --" or\n" --"\n" --" curl -F 'file=@\"localfile\";filename=\"nameinpost\"' url.com\n" --"\n" --" Note that if a filename/path is quoted by double-quotes, any\n" --, stdout); -- fputs( --" double-quote or backslash within the filename must be escaped by\n" --" backslash.\n" --"\n" --" See further examples and details in the MANUAL.\n" --"\n" --" This option can be used multiple times.\n" --"\n" --" --ftp-account [data]\n" --" (FTP) When an FTP server asks for \"account data\" after user name\n" --" and password has been provided, this data is sent off using the\n" --" ACCT command. (Added in 7.13.0)\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" --ftp-alternative-to-user \n" --" (FTP) If authenticating with the USER and PASS commands fails,\n" --" send this command. When connecting to Tumbleweed's Secure\n" --" Transport server over FTPS using a client certificate, using\n" --" \"SITE AUTH\" will tell the server to retrieve the username from\n" --" the certificate. (Added in 7.15.5)\n" --"\n" --, stdout); -- fputs( --" --ftp-create-dirs\n" --" (FTP/SFTP) When an FTP or SFTP URL/operation uses a path that\n" --" doesn't currently exist on the server, the standard behavior of\n" --" curl is to fail. Using this option, curl will instead attempt to\n" --" create missing directories.\n" --"\n" --" --ftp-method [method]\n" --" (FTP) Control what method curl should use to reach a file on an\n" --" FTP(S) server. The method argument should be one of the follow-\n" --, stdout); -- fputs( --" ing alternatives:\n" --"\n" --" multicwd\n" --" curl does a single CWD operation for each path part in\n" --" the given URL. For deep hierarchies this means very many\n" --" commands. This is how RFC 1738 says it should be done.\n" --" This is the default but the slowest behavior.\n" --"\n" --" nocwd curl does no CWD at all. curl will do SIZE, RETR, STOR\n" --, stdout); -- fputs( --" etc and give a full path to the server for all these com-\n" --" mands. This is the fastest behavior.\n" --"\n" --" singlecwd\n" --" curl does one CWD with the full target directory and then\n" --" operates on the file \"normally\" (like in the multicwd\n" --" case). This is somewhat more standards compliant than\n" --" 'nocwd' but without the full penalty of 'multicwd'.\n" --" (Added in 7.15.1)\n" --"\n" --, stdout); -- fputs( --" --ftp-pasv\n" --" (FTP) Use passive mode for the data connection. Passive is the\n" --" internal default behavior, but using this option can be used to\n" --" override a previous -P/-ftp-port option. (Added in 7.11.0)\n" --"\n" --" If this option is used several times, only the first one is\n" --" used. Undoing an enforced passive really isn't doable but you\n" --" must then instead enforce the correct -P, --ftp-port again.\n" --"\n" --, stdout); -- fputs( --" Passive mode means that curl will try the EPSV command first and\n" --" then PASV, unless --disable-epsv is used.\n" --"\n" --" --ftp-skip-pasv-ip\n" --" (FTP) Tell curl to not use the IP address the server suggests in\n" --" its response to curl's PASV command when curl connects the data\n" --" connection. Instead curl will re-use the same IP address it\n" --" already uses for the control connection. (Added in 7.14.2)\n" --"\n" --, stdout); -- fputs( --" This option has no effect if PORT, EPRT or EPSV is used instead\n" --" of PASV.\n" --"\n" --" --ftp-pret\n" --" (FTP) Tell curl to send a PRET command before PASV (and EPSV).\n" --" Certain FTP servers, mainly drftpd, require this non-standard\n" --" command for directory listings as well as up and downloads in\n" --" PASV mode. (Added in 7.20.x)\n" --"\n" --" --ftp-ssl-ccc\n" --, stdout); -- fputs( --" (FTP) Use CCC (Clear Command Channel) Shuts down the SSL/TLS\n" --" layer after authenticating. The rest of the control channel com-\n" --" munication will be unencrypted. This allows NAT routers to fol-\n" --" low the FTP transaction. The default mode is passive. See --ftp-\n" --" ssl-ccc-mode for other modes. (Added in 7.16.1)\n" --"\n" --" --ftp-ssl-ccc-mode [active/passive]\n" --, stdout); -- fputs( --" (FTP) Use CCC (Clear Command Channel) Sets the CCC mode. The\n" --" passive mode will not initiate the shutdown, but instead wait\n" --" for the server to do it, and will not reply to the shutdown from\n" --" the server. The active mode initiates the shutdown and waits for\n" --" a reply from the server. (Added in 7.16.2)\n" --"\n" --" --ftp-ssl-control\n" --" (FTP) Require SSL/TLS for the FTP login, clear for transfer.\n" --, stdout); -- fputs( --" Allows secure authentication, but non-encrypted data transfers\n" --" for efficiency. Fails the transfer if the server doesn't sup-\n" --" port SSL/TLS. (Added in 7.16.0) that can still be used but will\n" --" be removed in a future version.\n" --"\n" --" --form-string \n" --" (HTTP) Similar to --form except that the value string for the\n" --" named parameter is used literally. Leading '@' and '<' charac-\n" --, stdout); -- fputs( --" ters, and the ';type=' string in the value have no special mean-\n" --" ing. Use this in preference to --form if there's any possibility\n" --" that the string value may accidentally trigger the '@' or '<'\n" --" features of --form.\n" --"\n" --" -g, --globoff\n" --" This option switches off the \"URL globbing parser\". When you set\n" --" this option, you can specify URLs that contain the letters {}[]\n" --, stdout); -- fputs( --" without having them being interpreted by curl itself. Note that\n" --" these letters are not normal legal URL contents but they should\n" --" be encoded according to the URI standard.\n" --"\n" --" -G, --get\n" --" When used, this option will make all data specified with -d,\n" --" --data, --data-binary or --data-urlencode to be used in an HTTP\n" --" GET request instead of the POST request that otherwise would be\n" --, stdout); -- fputs( --" used. The data will be appended to the URL with a '?' separator.\n" --" If used in combination with -I, the POST data will instead be\n" --" appended to the URL with a HEAD request.\n" --"\n" --" If this option is used several times, only the first one is\n" --" used. This is because undoing a GET doesn't make sense, but you\n" --" should then instead enforce the alternative method you prefer.\n" --"\n" --" -H, --header
\n" --, stdout); -- fputs( --" (HTTP) Extra header to use when getting a web page. You may\n" --" specify any number of extra headers. Note that if you should add\n" --" a custom header that has the same name as one of the internal\n" --" ones curl would use, your externally set header will be used\n" --" instead of the internal one. This allows you to make even trick-\n" --" ier stuff than curl would normally do. You should not replace\n" --, stdout); -- fputs( --" internally set headers without knowing perfectly well what\n" --" you're doing. Remove an internal header by giving a replacement\n" --" without content on the right side of the colon, as in: -H\n" --" \"Host:\". If you send the custom header with no-value then its\n" --" header must be terminated with a semicolon, such as -H \"X-Cus-\n" --" tom-Header;\" to send \"X-Custom-Header:\".\n" --"\n" --, stdout); -- fputs( --" curl will make sure that each header you add/replace is sent\n" --" with the proper end-of-line marker, you should thus not add that\n" --" as a part of the header content: do not add newlines or carriage\n" --" returns, they will only mess things up for you.\n" --"\n" --" See also the -A, --user-agent and -e, --referer options.\n" --"\n" --" This option can be used multiple times to add/replace/remove\n" --" multiple headers.\n" --"\n" --, stdout); -- fputs( --" --hostpubmd5 \n" --" (SCP/SFTP) Pass a string containing 32 hexadecimal digits. The\n" --" string should be the 128 bit MD5 checksum of the remote host's\n" --" public key, curl will refuse the connection with the host unless\n" --" the md5sums match. (Added in 7.17.1)\n" --"\n" --" --ignore-content-length\n" --" (HTTP) Ignore the Content-Length header. This is particularly\n" --, stdout); -- fputs( --" useful for servers running Apache 1.x, which will report incor-\n" --" rect Content-Length for files larger than 2 gigabytes.\n" --"\n" --" -i, --include\n" --" (HTTP) Include the HTTP-header in the output. The HTTP-header\n" --" includes things like server-name, date of the document, HTTP-\n" --" version and more...\n" --"\n" --" -I, --head\n" --" (HTTP/FTP/FILE) Fetch the HTTP-header only! HTTP-servers feature\n" --, stdout); -- fputs( --" the command HEAD which this uses to get nothing but the header\n" --" of a document. When used on an FTP or FILE file, curl displays\n" --" the file size and last modification time only.\n" --"\n" --" --interface \n" --" Perform an operation using a specified interface. You can enter\n" --" interface name, IP address or host name. An example could look\n" --" like:\n" --"\n" --" curl --interface eth0:1 http://www.netscape.com/\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" -j, --junk-session-cookies\n" --" (HTTP) When curl is told to read cookies from a given file, this\n" --" option will make it discard all \"session cookies\". This will\n" --" basically have the same effect as if a new session is started.\n" --" Typical browsers always discard session cookies when they're\n" --" closed down.\n" --"\n" --" -J, --remote-header-name\n" --, stdout); -- fputs( --" (HTTP) This option tells the -O, --remote-name option to use the\n" --" server-specified Content-Disposition filename instead of\n" --" extracting a filename from the URL.\n" --"\n" --" There's no attempt to decode %-sequences (yet) in the provided\n" --" file name, so this option may provide you with rather unexpected\n" --" file names.\n" --"\n" --" -k, --insecure\n" --" (SSL) This option explicitly allows curl to perform \"insecure\"\n" --, stdout); -- fputs( --" SSL connections and transfers. All SSL connections are attempted\n" --" to be made secure by using the CA certificate bundle installed\n" --" by default. This makes all connections considered \"insecure\"\n" --" fail unless -k, --insecure is used.\n" --"\n" --" See this online resource for further details:\n" --" http://curl.haxx.se/docs/sslcerts.html\n" --"\n" --" -K, --config \n" --, stdout); -- fputs( --" Specify which config file to read curl arguments from. The con-\n" --" fig file is a text file in which command line arguments can be\n" --" written which then will be used as if they were written on the\n" --" actual command line.\n" --"\n" --" Options and their parameters must be specified on the same con-\n" --" fig file line, separated by whitespace, colon, or the equals\n" --, stdout); -- fputs( --" sign. Long option names can optionally be given in the config\n" --" file without the initial double dashes and if so, the colon or\n" --" equals characters can be used as separators. If the option is\n" --" specified with one or two dashes, there can be no colon or\n" --" equals character between the option and its parameter.\n" --"\n" --" If the parameter is to contain whitespace, the parameter must be\n" --, stdout); -- fputs( --" enclosed within quotes. Within double quotes, the following\n" --" escape sequences are available: \\\\, \\\", \\t, \\n, \\r and \\v. A\n" --" backslash preceding any other letter is ignored. If the first\n" --" column of a config line is a '#' character, the rest of the line\n" --" will be treated as a comment. Only write one option per physical\n" --" line in the config file.\n" --"\n" --, stdout); -- fputs( --" Specify the filename to -K, --config as '-' to make curl read\n" --" the file from stdin.\n" --"\n" --" Note that to be able to specify a URL in the config file, you\n" --" need to specify it using the --url option, and not by simply\n" --" writing the URL on its own line. So, it could look similar to\n" --" this:\n" --"\n" --" url = \"http://curl.haxx.se/docs/\"\n" --"\n" --, stdout); -- fputs( --" When curl is invoked, it always (unless -q is used) checks for a\n" --" default config file and uses it if found. The default config\n" --" file is checked for in the following places in this order:\n" --"\n" --" 1) curl tries to find the \"home dir\": It first checks for the\n" --" CURL_HOME and then the HOME environment variables. Failing that,\n" --" it uses getpwuid() on UNIX-like systems (which returns the home\n" --, stdout); -- fputs( --" dir given the current user in your system). On Windows, it then\n" --" checks for the APPDATA variable, or as a last resort the '%USER-\n" --" PROFILE%\\Application Data'.\n" --"\n" --" 2) On windows, if there is no _curlrc file in the home dir, it\n" --" checks for one in the same dir the curl executable is placed. On\n" --" UNIX-like systems, it will simply try to load .curlrc from the\n" --" determined home dir.\n" --"\n" --, stdout); -- fputs( --" # --- Example file ---\n" --" # this is a comment\n" --" url = \"curl.haxx.se\"\n" --" output = \"curlhere.html\"\n" --" user-agent = \"superagent/1.0\"\n" --"\n" --" # and fetch another URL too\n" --" url = \"curl.haxx.se/docs/manpage.html\"\n" --" -O\n" --" referer = \"http://nowhereatall.com/\"\n" --" # --- End of example file ---\n" --"\n" --" This option can be used multiple times to load multiple config\n" --" files.\n" --"\n" --, stdout); -- fputs( --" --keepalive-time \n" --" This option sets the time a connection needs to remain idle\n" --" before sending keepalive probes and the time between individual\n" --" keepalive probes. It is currently effective on operating systems\n" --" offering the TCP_KEEPIDLE and TCP_KEEPINTVL socket options\n" --" (meaning Linux, recent AIX, HP-UX and more). This option has no\n" --" effect if --no-keepalive is used. (Added in 7.18.0)\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --" If unspecified, the option defaults to 60 seconds.\n" --"\n" --" --key \n" --" (SSL/SSH) Private key file name. Allows you to provide your pri-\n" --" vate key in this separate file.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --key-type \n" --" (SSL) Private key file type. Specify which type your --key pro-\n" --, stdout); -- fputs( --" vided private key is. DER, PEM, and ENG are supported. If not\n" --" specified, PEM is assumed.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --krb \n" --" (FTP) Enable Kerberos authentication and use. The level must be\n" --" entered and should be one of 'clear', 'safe', 'confidential', or\n" --" 'private'. Should you use a level that is not one of these,\n" --, stdout); -- fputs( --" 'private' will instead be used.\n" --"\n" --" This option requires a library built with kerberos4 or GSSAPI\n" --" (GSS-Negotiate) support. This is not very common. Use -V, --ver-\n" --" sion to see if your curl supports it.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -l, --list-only\n" --" (FTP) When listing an FTP directory, this switch forces a name-\n" --, stdout); -- fputs( --" only view. This is especially useful if the user wants to\n" --" machine-parse the contents of an FTP directory since the normal\n" --" directory view doesn't use a standard look or format. When used\n" --" like this, the option causes a NLST command to be sent to the\n" --" server instead of LIST.\n" --"\n" --" Note: Some FTP servers list only files in their response to\n" --, stdout); -- fputs( --" NLST; they do not include sub-directories and symbolic links.\n" --"\n" --" (POP3) When retrieving a specific email from POP3, this switch\n" --" forces a LIST command to be performed instead of RETR. This is\n" --" particularly useful if the user wants to see if a specific mes-\n" --" sage id exists on the server and what size it is.\n" --"\n" --" Note: When combined with -X, --request , this option\n" --, stdout); -- fputs( --" can be used to send an UIDL command instead, so the user may use\n" --" the email's unique identifier rather than it's message id to\n" --" make the request. (Added in 7.21.5)\n" --"\n" --" -L, --location\n" --" (HTTP/HTTPS) If the server reports that the requested page has\n" --" moved to a different location (indicated with a Location: header\n" --" and a 3XX response code), this option will make curl redo the\n" --, stdout); -- fputs( --" request on the new place. If used together with -i, --include or\n" --" -I, --head, headers from all requested pages will be shown. When\n" --" authentication is used, curl only sends its credentials to the\n" --" initial host. If a redirect takes curl to a different host, it\n" --" won't be able to intercept the user+password. See also --loca-\n" --" tion-trusted on how to change this. You can limit the amount of\n" --, stdout); -- fputs( --" redirects to follow by using the --max-redirs option.\n" --"\n" --" When curl follows a redirect and the request is not a plain GET\n" --" (for example POST or PUT), it will do the following request with\n" --" a GET if the HTTP response was 301, 302, or 303. If the response\n" --" code was any other 3xx code, curl will re-send the following\n" --" request using the same unmodified method.\n" --"\n" --" --libcurl \n" --, stdout); -- fputs( --" Append this option to any ordinary curl command line, and you\n" --" will get a libcurl-using C source code written to the file that\n" --" does the equivalent of what your command-line operation does!\n" --"\n" --" If this option is used several times, the last given file name\n" --" will be used. (Added in 7.16.1)\n" --"\n" --" --limit-rate \n" --" Specify the maximum transfer rate you want curl to use. This\n" --, stdout); -- fputs( --" feature is useful if you have a limited pipe and you'd like your\n" --" transfer not to use your entire bandwidth.\n" --"\n" --" The given speed is measured in bytes/second, unless a suffix is\n" --" appended. Appending 'k' or 'K' will count the number as kilo-\n" --" bytes, 'm' or M' makes it megabytes, while 'g' or 'G' makes it\n" --" gigabytes. Examples: 200K, 3m and 1G.\n" --"\n" --, stdout); -- fputs( --" The given rate is the average speed counted during the entire\n" --" transfer. It means that curl might use higher transfer speeds in\n" --" short bursts, but over time it uses no more than the given rate.\n" --" If you also use the -Y, --speed-limit option, that option will\n" --" take precedence and might cripple the rate-limiting slightly, to\n" --" help keeping the speed-limit logic working.\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" --local-port [-num]\n" --" Set a preferred number or range of local port numbers to use for\n" --" the connection(s). Note that port numbers by nature are a\n" --" scarce resource that will be busy at times so setting this range\n" --" to something too narrow might cause unnecessary connection setup\n" --" failures. (Added in 7.15.2)\n" --"\n" --" --location-trusted\n" --, stdout); -- fputs( --" (HTTP/HTTPS) Like -L, --location, but will allow sending the\n" --" name + password to all hosts that the site may redirect to. This\n" --" may or may not introduce a security breach if the site redirects\n" --" you to a site to which you'll send your authentication info\n" --" (which is plaintext in the case of HTTP Basic authentication).\n" --"\n" --" -m, --max-time \n" --, stdout); -- fputs( --" Maximum time in seconds that you allow the whole operation to\n" --" take. This is useful for preventing your batch jobs from hang-\n" --" ing for hours due to slow networks or links going down. Since\n" --" 7.32.0, this option accepts decimal values, but the actual time-\n" --" out will decrease in accuracy as the specified timeout increases\n" --" in decimal precision. See also the --connect-timeout option.\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" --mail-auth
\n" --" (SMTP) Specify a single address. This will be used to specify\n" --" the authentication address (identity) of a submitted message\n" --" that is being relayed to another server.\n" --"\n" --" (Added in 7.25.0)\n" --"\n" --" --mail-from
\n" --" (SMTP) Specify a single address that the given mail should get\n" --" sent from.\n" --"\n" --, stdout); -- fputs( --" (Added in 7.20.0)\n" --"\n" --" --max-filesize \n" --" Specify the maximum size (in bytes) of a file to download. If\n" --" the file requested is larger than this value, the transfer will\n" --" not start and curl will return with exit code 63.\n" --"\n" --" NOTE: The file size is not always known prior to download, and\n" --" for such files this option has no effect even if the file trans-\n" --, stdout); -- fputs( --" fer ends up being larger than this given limit. This concerns\n" --" both FTP and HTTP transfers.\n" --"\n" --" --mail-rcpt
\n" --" (SMTP) Specify a single address, user name or mailing list name.\n" --" When performing a mail transfer, the recipient should specify a\n" --" valid email address to send the mail to. (Added in 7.20.0)\n" --"\n" --" When performing an address verification (VRFY command), the\n" --, stdout); -- fputs( --" recipient should be specified as the user name or user name and\n" --" domain (as per Section 3.5 of RFC5321). (Added in 7.34.0)\n" --"\n" --" When performing a mailing list expand (EXPN command), the recip-\n" --" ient should be specified using the mailing list name, such as\n" --" \"Friends\" or \"London-Office\". (Added in 7.34.0)\n" --"\n" --" --max-redirs \n" --" Set maximum number of redirection-followings allowed. If -L,\n" --, stdout); -- fputs( --" --location is used, this option can be used to prevent curl from\n" --" following redirections \"in absurdum\". By default, the limit is\n" --" set to 50 redirections. Set this option to -1 to make it limit-\n" --" less.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --metalink\n" --" This option can tell curl to parse and process a given URI as\n" --, stdout); -- fputs( --" Metalink file (both version 3 and 4 (RFC 5854) are supported)\n" --" and make use of the mirrors listed within for failover if there\n" --" are errors (such as the file or server not being available). It\n" --" will also verify the hash of the file after the download com-\n" --" pletes. The Metalink file itself is downloaded and processed in\n" --" memory and not stored in the local file system.\n" --"\n" --, stdout); -- fputs( --" Example to use a remote Metalink file:\n" --"\n" --" curl --metalink http://www.example.com/example.metalink\n" --"\n" --" To use a Metalink file in the local file system, use FILE proto-\n" --" col (file://):\n" --"\n" --" curl --metalink file://example.metalink\n" --"\n" --" Please note that if FILE protocol is disabled, there is no way\n" --" to use a local Metalink file at the time of this writing. Also\n" --, stdout); -- fputs( --" note that if --metalink and --include are used together,\n" --" --include will be ignored. This is because including headers in\n" --" the response will break Metalink parser and if the headers are\n" --" included in the file described in Metalink file, hash check will\n" --" fail.\n" --"\n" --" (Added in 7.27.0, if built against the libmetalink library.)\n" --"\n" --" -n, --netrc\n" --, stdout); -- fputs( --" Makes curl scan the .netrc (_netrc on Windows) file in the\n" --" user's home directory for login name and password. This is typi-\n" --" cally used for FTP on UNIX. If used with HTTP, curl will enable\n" --" user authentication. See netrc(4) or ftp(1) for details on the\n" --" file format. Curl will not complain if that file doesn't have\n" --" the right permissions (it should not be either world- or group-\n" --, stdout); -- fputs( --" readable). The environment variable \"HOME\" is used to find the\n" --" home directory.\n" --"\n" --" A quick and very simple example of how to setup a .netrc to\n" --" allow curl to FTP to the machine host.domain.com with user name\n" --" 'myself' and password 'secret' should look similar to:\n" --"\n" --" machine host.domain.com login myself password secret\n" --"\n" --" -N, --no-buffer\n" --, stdout); -- fputs( --" Disables the buffering of the output stream. In normal work sit-\n" --" uations, curl will use a standard buffered output stream that\n" --" will have the effect that it will output the data in chunks, not\n" --" necessarily exactly when the data arrives. Using this option\n" --" will disable that buffering.\n" --"\n" --" Note that this is the negated option name documented. You can\n" --" thus use --buffer to enforce the buffering.\n" --"\n" --, stdout); -- fputs( --" --netrc-file\n" --" This option is similar to --netrc, except that you provide the\n" --" path (absolute or relative) to the netrc file that Curl should\n" --" use. You can only specify one netrc file per invocation. If\n" --" several --netrc-file options are provided, only the last one\n" --" will be used. (Added in 7.21.5)\n" --"\n" --" This option overrides any use of --netrc as they are mutually\n" --, stdout); -- fputs( --" exclusive. It will also abide by --netrc-optional if specified.\n" --"\n" --" --netrc-optional\n" --" Very similar to --netrc, but this option makes the .netrc usage\n" --" optional and not mandatory as the --netrc option does.\n" --"\n" --" --negotiate\n" --" (HTTP) Enables GSS-Negotiate authentication. The GSS-Negotiate\n" --" method was designed by Microsoft and is used in their web appli-\n" --, stdout); -- fputs( --" cations. It is primarily meant as a support for Kerberos5\n" --" authentication but may be also used along with another authenti-\n" --" cation method. For more information see IETF draft draft-brezak-\n" --" spnego-http-04.txt.\n" --"\n" --" If you want to enable Negotiate for your proxy authentication,\n" --" then use --proxy-negotiate.\n" --"\n" --" This option requires a library built with GSSAPI support. This\n" --, stdout); -- fputs( --" is not very common. Use -V, --version to see if your version\n" --" supports GSS-Negotiate.\n" --"\n" --" When using this option, you must also provide a fake -u, --user\n" --" option to activate the authentication code properly. Sending a\n" --" '-u :' is enough as the user name and password from the -u\n" --" option aren't actually used.\n" --"\n" --" If this option is used several times, only the first one is\n" --" used.\n" --"\n" --, stdout); -- fputs( --" --no-keepalive\n" --" Disables the use of keepalive messages on the TCP connection, as\n" --" by default curl enables them.\n" --"\n" --" Note that this is the negated option name documented. You can\n" --" thus use --keepalive to enforce keepalive.\n" --"\n" --" --no-sessionid\n" --" (SSL) Disable curl's use of SSL session-ID caching. By default\n" --" all transfers are done using the cache. Note that while nothing\n" --, stdout); -- fputs( --" should ever get hurt by attempting to reuse SSL session-IDs,\n" --" there seem to be broken SSL implementations in the wild that may\n" --" require you to disable this in order for you to succeed. (Added\n" --" in 7.16.0)\n" --"\n" --" Note that this is the negated option name documented. You can\n" --" thus use --sessionid to enforce session-ID caching.\n" --"\n" --" --noproxy \n" --, stdout); -- fputs( --" Comma-separated list of hosts which do not use a proxy, if one\n" --" is specified. The only wildcard is a single * character, which\n" --" matches all hosts, and effectively disables the proxy. Each name\n" --" in this list is matched as either a domain which contains the\n" --" hostname, or the hostname itself. For example, local.com would\n" --" match local.com, local.com:80, and www.local.com, but not\n" --, stdout); -- fputs( --" www.notlocal.com. (Added in 7.19.4).\n" --"\n" --" --ntlm (HTTP) Enables NTLM authentication. The NTLM authentication\n" --" method was designed by Microsoft and is used by IIS web servers.\n" --" It is a proprietary protocol, reverse-engineered by clever peo-\n" --" ple and implemented in curl based on their efforts. This kind of\n" --" behavior should not be endorsed, you should encourage everyone\n" --, stdout); -- fputs( --" who uses NTLM to switch to a public and documented authentica-\n" --" tion method instead, such as Digest.\n" --"\n" --" If you want to enable NTLM for your proxy authentication, then\n" --" use --proxy-ntlm.\n" --"\n" --" This option requires a library built with SSL support. Use -V,\n" --" --version to see if your curl supports NTLM.\n" --"\n" --" If this option is used several times, only the first one is\n" --" used.\n" --"\n" --, stdout); -- fputs( --" -o, --output \n" --" Write output to instead of stdout. If you are using {} or\n" --" [] to fetch multiple documents, you can use '#' followed by a\n" --" number in the specifier. That variable will be replaced\n" --" with the current string for the URL being fetched. Like in:\n" --"\n" --" curl http://{one,two}.site.com -o \"file_#1.txt\"\n" --"\n" --" or use several variables like:\n" --"\n" --, stdout); -- fputs( --" curl http://{site,host}.host[1-5].com -o \"#1_#2\"\n" --"\n" --" You may use this option as many times as the number of URLs you\n" --" have.\n" --"\n" --" See also the --create-dirs option to create the local directo-\n" --" ries dynamically. Specifying the output as '-' (a single dash)\n" --" will force the output to be done to stdout.\n" --"\n" --" -O, --remote-name\n" --" Write output to a local file named like the remote file we get.\n" --, stdout); -- fputs( --" (Only the file part of the remote file is used, the path is cut\n" --" off.)\n" --"\n" --" The remote file name to use for saving is extracted from the\n" --" given URL, nothing else.\n" --"\n" --" Consequentially, the file will be saved in the current working\n" --" directory. If you want the file saved in a different directory,\n" --" make sure you change current working directory before you invoke\n" --, stdout); -- fputs( --" curl with the -O, --remote-name flag!\n" --"\n" --" There is no URL decoding done on the file name. If it has %20 or\n" --" other URL encoded parts of the name, they will end up as-is as\n" --" file name.\n" --"\n" --" You may use this option as many times as the number of URLs you\n" --" have.\n" --"\n" --" --oauth2-bearer\n" --" (IMAP, POP3, SMTP) Specify the Bearer Token for OAUTH 2.0 server\n" --, stdout); -- fputs( --" authentication. The Bearer Token is used in conjunction with the\n" --" user name which can be specified as part of the --url or -u,\n" --" --user options.\n" --"\n" --" The Bearer Token and user name are formatted according to RFC\n" --" 6750.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -p, --proxytunnel\n" --" When an HTTP proxy is used (-x, --proxy), this option will cause\n" --, stdout); -- fputs( --" non-HTTP protocols to attempt to tunnel through the proxy\n" --" instead of merely using it to do HTTP-like operations. The tun-\n" --" nel approach is made with the HTTP proxy CONNECT request and\n" --" requires that the proxy allows direct connect to the remote port\n" --" number curl wants to tunnel through to.\n" --"\n" --" -P, --ftp-port
\n" --" (FTP) Reverses the default initiator/listener roles when con-\n" --, stdout); -- fputs( --" necting with FTP. This switch makes curl use active mode. In\n" --" practice, curl then tells the server to connect back to the\n" --" client's specified address and port, while passive mode asks the\n" --" server to setup an IP address and port for it to connect to.\n" --"
should be one of:\n" --"\n" --" interface\n" --" i.e \"eth0\" to specify which interface's IP address you\n" --, stdout); -- fputs( --" want to use (Unix only)\n" --"\n" --" IP address\n" --" i.e \"192.168.10.1\" to specify the exact IP address\n" --"\n" --" host name\n" --" i.e \"my.host.domain\" to specify the machine\n" --"\n" --" - make curl pick the same IP address that is already used\n" --" for the control connection\n" --"\n" --" If this option is used several times, the last one will be used. Dis-\n" --, stdout); -- fputs( --" able the use of PORT with --ftp-pasv. Disable the attempt to use the\n" --" EPRT command instead of PORT by using --disable-eprt. EPRT is really\n" --" PORT++.\n" --"\n" --" Starting in 7.19.5, you can append \":[start]-[end]\" to the right of the\n" --" address, to tell curl what TCP port range to use. That means you spec-\n" --" ify a port range, from a lower to a higher number. A single number\n" --" works as well, but do note that it increases the risk of failure since\n" --, stdout); -- fputs( --" the port may not be available.\n" --"\n" --" --pass \n" --" (SSL/SSH) Passphrase for the private key\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --post301\n" --" (HTTP) Tells curl to respect RFC 2616/10.3.2 and not convert\n" --" POST requests into GET requests when following a 301 redirect-\n" --" ion. The non-RFC behaviour is ubiquitous in web browsers, so\n" --, stdout); -- fputs( --" curl does the conversion by default to maintain consistency.\n" --" However, a server may require a POST to remain a POST after such\n" --" a redirection. This option is meaningful only when using -L,\n" --" --location (Added in 7.17.1)\n" --"\n" --" --post302\n" --" (HTTP) Tells curl to respect RFC 2616/10.3.2 and not convert\n" --" POST requests into GET requests when following a 302 redirect-\n" --, stdout); -- fputs( --" ion. The non-RFC behaviour is ubiquitous in web browsers, so\n" --" curl does the conversion by default to maintain consistency.\n" --" However, a server may require a POST to remain a POST after such\n" --" a redirection. This option is meaningful only when using -L,\n" --" --location (Added in 7.19.1)\n" --"\n" --" --post303\n" --" (HTTP) Tells curl to respect RFC 2616/10.3.2 and not convert\n" --, stdout); -- fputs( --" POST requests into GET requests when following a 303 redirect-\n" --" ion. The non-RFC behaviour is ubiquitous in web browsers, so\n" --" curl does the conversion by default to maintain consistency.\n" --" However, a server may require a POST to remain a POST after such\n" --" a redirection. This option is meaningful only when using -L,\n" --" --location (Added in 7.26.0)\n" --"\n" --" --proto \n" --, stdout); -- fputs( --" Tells curl to use the listed protocols for its initial\n" --" retrieval. Protocols are evaluated left to right, are comma sep-\n" --" arated, and are each a protocol name or 'all', optionally pre-\n" --" fixed by zero or more modifiers. Available modifiers are:\n" --"\n" --" + Permit this protocol in addition to protocols already permit-\n" --" ted (this is the default if no modifier is used).\n" --"\n" --, stdout); -- fputs( --" - Deny this protocol, removing it from the list of protocols\n" --" already permitted.\n" --"\n" --" = Permit only this protocol (ignoring the list already permit-\n" --" ted), though subject to later modification by subsequent\n" --" entries in the comma separated list.\n" --"\n" --" For example:\n" --"\n" --" --proto -ftps uses the default protocols, but disables ftps\n" --"\n" --" --proto -all,https,+http\n" --, stdout); -- fputs( --" only enables http and https\n" --"\n" --" --proto =http,https\n" --" also only enables http and https\n" --"\n" --" Unknown protocols produce a warning. This allows scripts to\n" --" safely rely on being able to disable potentially dangerous pro-\n" --" tocols, without relying upon support for that protocol being\n" --" built into curl to avoid an error.\n" --"\n" --, stdout); -- fputs( --" This option can be used multiple times, in which case the effect\n" --" is the same as concatenating the protocols into one instance of\n" --" the option.\n" --"\n" --" (Added in 7.20.2)\n" --"\n" --" --proto-redir \n" --" Tells curl to use the listed protocols after a redirect. See\n" --" --proto for how protocols are represented.\n" --"\n" --" (Added in 7.20.2)\n" --"\n" --" --proxy-anyauth\n" --, stdout); -- fputs( --" Tells curl to pick a suitable authentication method when commu-\n" --" nicating with the given proxy. This might cause an extra\n" --" request/response round-trip. (Added in 7.13.2)\n" --"\n" --" --proxy-basic\n" --" Tells curl to use HTTP Basic authentication when communicating\n" --" with the given proxy. Use --basic for enabling HTTP Basic with a\n" --" remote host. Basic is the default authentication method curl\n" --, stdout); -- fputs( --" uses with proxies.\n" --"\n" --" --proxy-digest\n" --" Tells curl to use HTTP Digest authentication when communicating\n" --" with the given proxy. Use --digest for enabling HTTP Digest with\n" --" a remote host.\n" --"\n" --" --proxy-negotiate\n" --" Tells curl to use HTTP Negotiate authentication when communicat-\n" --" ing with the given proxy. Use --negotiate for enabling HTTP\n" --" Negotiate with a remote host. (Added in 7.17.1)\n" --"\n" --, stdout); -- fputs( --" --proxy-ntlm\n" --" Tells curl to use HTTP NTLM authentication when communicating\n" --" with the given proxy. Use --ntlm for enabling NTLM with a remote\n" --" host.\n" --"\n" --" --proxy1.0 \n" --" Use the specified HTTP 1.0 proxy. If the port number is not\n" --" specified, it is assumed at port 1080.\n" --"\n" --" The only difference between this and the HTTP proxy option (-x,\n" --, stdout); -- fputs( --" --proxy), is that attempts to use CONNECT through the proxy will\n" --" specify an HTTP 1.0 protocol instead of the default HTTP 1.1.\n" --"\n" --" --pubkey \n" --" (SSH) Public key file name. Allows you to provide your public\n" --" key in this separate file.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -q If used as the first parameter on the command line, the curlrc\n" --, stdout); -- fputs( --" config file will not be read and used. See the -K, --config for\n" --" details on the default config file search path.\n" --"\n" --" -Q, --quote \n" --" (FTP/SFTP) Send an arbitrary command to the remote FTP or SFTP\n" --" server. Quote commands are sent BEFORE the transfer takes place\n" --" (just after the initial PWD command in an FTP transfer, to be\n" --" exact). To make commands take place after a successful transfer,\n" --, stdout); -- fputs( --" prefix them with a dash '-'. To make commands be sent after\n" --" curl has changed the working directory, just before the transfer\n" --" command(s), prefix the command with a '+' (this is only sup-\n" --" ported for FTP). You may specify any number of commands. If the\n" --" server returns failure for one of the commands, the entire oper-\n" --" ation will be aborted. You must send syntactically correct FTP\n" --, stdout); -- fputs( --" commands as RFC 959 defines to FTP servers, or one of the com-\n" --" mands listed below to SFTP servers. This option can be used\n" --" multiple times. When speaking to an FTP server, prefix the com-\n" --" mand with an asterisk (*) to make curl continue even if the com-\n" --" mand fails as by default curl will stop at first failure.\n" --"\n" --" SFTP is a binary protocol. Unlike for FTP, curl interprets SFTP\n" --, stdout); -- fputs( --" quote commands itself before sending them to the server. File\n" --" names may be quoted shell-style to embed spaces or special char-\n" --" acters. Following is the list of all supported SFTP quote com-\n" --" mands:\n" --"\n" --" chgrp group file\n" --" The chgrp command sets the group ID of the file named by\n" --" the file operand to the group ID specified by the group\n" --, stdout); -- fputs( --" operand. The group operand is a decimal integer group ID.\n" --"\n" --" chmod mode file\n" --" The chmod command modifies the file mode bits of the\n" --" specified file. The mode operand is an octal integer mode\n" --" number.\n" --"\n" --" chown user file\n" --" The chown command sets the owner of the file named by the\n" --" file operand to the user ID specified by the user oper-\n" --, stdout); -- fputs( --" and. The user operand is a decimal integer user ID.\n" --"\n" --" ln source_file target_file\n" --" The ln and symlink commands create a symbolic link at the\n" --" target_file location pointing to the source_file loca-\n" --" tion.\n" --"\n" --" mkdir directory_name\n" --" The mkdir command creates the directory named by the\n" --" directory_name operand.\n" --"\n" --, stdout); -- fputs( --" pwd The pwd command returns the absolute pathname of the cur-\n" --" rent working directory.\n" --"\n" --" rename source target\n" --" The rename command renames the file or directory named by\n" --" the source operand to the destination path named by the\n" --" target operand.\n" --"\n" --" rm file\n" --" The rm command removes the file specified by the file op-\n" --" erand.\n" --"\n" --, stdout); -- fputs( --" rmdir directory\n" --" The rmdir command removes the directory entry specified\n" --" by the directory operand, provided it is empty.\n" --"\n" --" symlink source_file target_file\n" --" See ln.\n" --"\n" --" -r, --range \n" --" (HTTP/FTP/SFTP/FILE) Retrieve a byte range (i.e a partial docu-\n" --" ment) from a HTTP/1.1, FTP or SFTP server or a local FILE.\n" --" Ranges can be specified in a number of ways.\n" --"\n" --, stdout); -- fputs( --" 0-499 specifies the first 500 bytes\n" --"\n" --" 500-999 specifies the second 500 bytes\n" --"\n" --" -500 specifies the last 500 bytes\n" --"\n" --" 9500- specifies the bytes from offset 9500 and forward\n" --"\n" --" 0-0,-1 specifies the first and last byte only(*)(H)\n" --"\n" --" 500-700,600-799\n" --" specifies 300 bytes from offset 500(H)\n" --"\n" --" 100-199,500-599\n" --, stdout); -- fputs( --" specifies two separate 100-byte ranges(*)(H)\n" --"\n" --" (*) = NOTE that this will cause the server to reply with a multipart\n" --" response!\n" --"\n" --" Only digit characters (0-9) are valid in the 'start' and 'stop' fields\n" --" of the 'start-stop' range syntax. If a non-digit character is given in\n" --" the range, the server's response will be unspecified, depending on the\n" --" server's configuration.\n" --"\n" --, stdout); -- fputs( --" You should also be aware that many HTTP/1.1 servers do not have this\n" --" feature enabled, so that when you attempt to get a range, you'll\n" --" instead get the whole document.\n" --"\n" --" FTP and SFTP range downloads only support the simple 'start-stop' syn-\n" --" tax (optionally with one of the numbers omitted). FTP use depends on\n" --" the extended FTP command SIZE.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -R, --remote-time\n" --, stdout); -- fputs( --" When used, this will make curl attempt to figure out the time-\n" --" stamp of the remote file, and if that is available make the\n" --" local file get that same timestamp.\n" --"\n" --" --random-file \n" --" (SSL) Specify the path name to file containing what will be con-\n" --" sidered as random data. The data is used to seed the random\n" --" engine for SSL connections. See also the --egd-file option.\n" --"\n" --, stdout); -- fputs( --" --raw (HTTP) When used, it disables all internal HTTP decoding of con-\n" --" tent or transfer encodings and instead makes them passed on\n" --" unaltered, raw. (Added in 7.16.2)\n" --"\n" --" --remote-name-all\n" --" This option changes the default action for all given URLs to be\n" --" dealt with as if -O, --remote-name were used for each one. So if\n" --" you want to disable that for a specific URL after --remote-name-\n" --, stdout); -- fputs( --" all has been used, you must use \"-o -\" or --no-remote-name.\n" --" (Added in 7.19.0)\n" --"\n" --" --resolve \n" --" Provide a custom address for a specific host and port pair.\n" --" Using this, you can make the curl requests(s) use a specified\n" --" address and prevent the otherwise normally resolved address to\n" --" be used. Consider it a sort of /etc/hosts alternative provided\n" --, stdout); -- fputs( --" on the command line. The port number should be the number used\n" --" for the specific protocol the host will be used for. It means\n" --" you need several entries if you want to provide address for the\n" --" same host but different ports.\n" --"\n" --" This option can be used many times to add many host names to\n" --" resolve.\n" --"\n" --" (Added in 7.21.3)\n" --"\n" --" --retry \n" --, stdout); -- fputs( --" If a transient error is returned when curl tries to perform a\n" --" transfer, it will retry this number of times before giving up.\n" --" Setting the number to 0 makes curl do no retries (which is the\n" --" default). Transient error means either: a timeout, an FTP 4xx\n" --" response code or an HTTP 5xx response code.\n" --"\n" --" When curl is about to retry a transfer, it will first wait one\n" --, stdout); -- fputs( --" second and then for all forthcoming retries it will double the\n" --" waiting time until it reaches 10 minutes which then will be the\n" --" delay between the rest of the retries. By using --retry-delay\n" --" you disable this exponential backoff algorithm. See also\n" --" --retry-max-time to limit the total time allowed for retries.\n" --" (Added in 7.12.3)\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" --retry-delay \n" --" Make curl sleep this amount of time before each retry when a\n" --" transfer has failed with a transient error (it changes the\n" --" default backoff time algorithm between retries). This option is\n" --" only interesting if --retry is also used. Setting this delay to\n" --, stdout); -- fputs( --" zero will make curl use the default backoff time. (Added in\n" --" 7.12.3)\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --retry-max-time \n" --" The retry timer is reset before the first transfer attempt.\n" --" Retries will be done as usual (see --retry) as long as the timer\n" --" hasn't reached this given limit. Notice that if the timer hasn't\n" --, stdout); -- fputs( --" reached the limit, the request will be made and while perform-\n" --" ing, it may take longer than this given time period. To limit a\n" --" single request's maximum time, use -m, --max-time. Set this\n" --" option to zero to not timeout retries. (Added in 7.12.3)\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -s, --silent\n" --" Silent or quiet mode. Don't show progress meter or error mes-\n" --, stdout); -- fputs( --" sages. Makes Curl mute. It will still output the data you ask\n" --" for, potentially even to the terminal/stdout unless you redirect\n" --" it.\n" --"\n" --" --sasl-ir\n" --" Enable initial response in SASL authentication. (Added in\n" --" 7.31.0)\n" --"\n" --" -S, --show-error\n" --" When used with -s it makes curl show an error message if it\n" --" fails.\n" --"\n" --" --ssl (FTP, POP3, IMAP, SMTP) Try to use SSL/TLS for the connection.\n" --, stdout); -- fputs( --" Reverts to a non-secure connection if the server doesn't support\n" --" SSL/TLS. See also --ftp-ssl-control and --ssl-reqd for differ-\n" --" ent levels of encryption required. (Added in 7.20.0)\n" --"\n" --" This option was formerly known as --ftp-ssl (Added in 7.11.0).\n" --" That option name can still be used but will be removed in a\n" --" future version.\n" --"\n" --" --ssl-reqd\n" --, stdout); -- fputs( --" (FTP, POP3, IMAP, SMTP) Require SSL/TLS for the connection.\n" --" Terminates the connection if the server doesn't support SSL/TLS.\n" --" (Added in 7.20.0)\n" --"\n" --" This option was formerly known as --ftp-ssl-reqd (added in\n" --" 7.15.5). That option name can still be used but will be removed\n" --" in a future version.\n" --"\n" --" --ssl-allow-beast\n" --" (SSL) This option tells curl to not work around a security flaw\n" --, stdout); -- fputs( --" in the SSL3 and TLS1.0 protocols known as BEAST. If this option\n" --" isn't used, the SSL layer may use workarounds known to cause\n" --" interoperability problems with some older SSL implementations.\n" --" WARNING: this option loosens the SSL security, and by using this\n" --" flag you ask for exactly that. (Added in 7.25.0)\n" --"\n" --" --socks4 \n" --" Use the specified SOCKS4 proxy. If the port number is not speci-\n" --, stdout); -- fputs( --" fied, it is assumed at port 1080. (Added in 7.15.2)\n" --"\n" --" This option overrides any previous use of -x, --proxy, as they\n" --" are mutually exclusive.\n" --"\n" --" Since 7.21.7, this option is superfluous since you can specify a\n" --" socks4 proxy with -x, --proxy using a socks4:// protocol prefix.\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --socks4a \n" --, stdout); -- fputs( --" Use the specified SOCKS4a proxy. If the port number is not spec-\n" --" ified, it is assumed at port 1080. (Added in 7.18.0)\n" --"\n" --" This option overrides any previous use of -x, --proxy, as they\n" --" are mutually exclusive.\n" --"\n" --" Since 7.21.7, this option is superfluous since you can specify a\n" --" socks4a proxy with -x, --proxy using a socks4a:// protocol pre-\n" --" fix.\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" --socks5-hostname \n" --" Use the specified SOCKS5 proxy (and let the proxy resolve the\n" --" host name). If the port number is not specified, it is assumed\n" --" at port 1080. (Added in 7.18.0)\n" --"\n" --" This option overrides any previous use of -x, --proxy, as they\n" --" are mutually exclusive.\n" --"\n" --, stdout); -- fputs( --" Since 7.21.7, this option is superfluous since you can specify a\n" --" socks5 hostname proxy with -x, --proxy using a socks5h:// proto-\n" --" col prefix.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --" (This option was previously wrongly documented and used as\n" --" --socks without the number appended.)\n" --"\n" --" --socks5 \n" --, stdout); -- fputs( --" Use the specified SOCKS5 proxy - but resolve the host name\n" --" locally. If the port number is not specified, it is assumed at\n" --" port 1080.\n" --"\n" --" This option overrides any previous use of -x, --proxy, as they\n" --" are mutually exclusive.\n" --"\n" --" Since 7.21.7, this option is superfluous since you can specify a\n" --" socks5 proxy with -x, --proxy using a socks5:// protocol prefix.\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --" (This option was previously wrongly documented and used as\n" --" --socks without the number appended.)\n" --"\n" --" This option (as well as --socks4) does not work with IPV6, FTPS\n" --" or LDAP.\n" --"\n" --" --socks5-gssapi-service \n" --" The default service name for a socks server is rcmd/server-fqdn.\n" --" This option allows you to change it.\n" --"\n" --, stdout); -- fputs( --" Examples: --socks5 proxy-name --socks5-gssapi-service sockd\n" --" would use sockd/proxy-name --socks5 proxy-name --socks5-gssapi-\n" --" service sockd/real-name would use sockd/real-name for cases\n" --" where the proxy-name does not match the principal name. (Added\n" --" in 7.19.4).\n" --"\n" --" --socks5-gssapi-nec\n" --" As part of the gssapi negotiation a protection mode is negoti-\n" --, stdout); -- fputs( --" ated. RFC 1961 says in section 4.3/4.4 it should be protected,\n" --" but the NEC reference implementation does not. The option\n" --" --socks5-gssapi-nec allows the unprotected exchange of the pro-\n" --" tection mode negotiation. (Added in 7.19.4).\n" --"\n" --" --stderr \n" --" Redirect all writes to stderr to the specified file instead. If\n" --" the file name is a plain '-', it is instead written to stdout.\n" --"\n" --, stdout); -- fputs( --" If this option is used several times, the last one will be used.\n" --"\n" --" -t, --telnet-option \n" --" Pass options to the telnet protocol. Supported options are:\n" --"\n" --" TTYPE= Sets the terminal type.\n" --"\n" --" XDISPLOC= Sets the X display location.\n" --"\n" --" NEW_ENV= Sets an environment variable.\n" --"\n" --" -T, --upload-file \n" --" This transfers the specified local file to the remote URL. If\n" --, stdout); -- fputs( --" there is no file part in the specified URL, Curl will append the\n" --" local file name. NOTE that you must use a trailing / on the last\n" --" directory to really prove to Curl that there is no file name or\n" --" curl will think that your last directory name is the remote file\n" --" name to use. That will most likely cause the upload operation to\n" --" fail. If this is used on an HTTP(S) server, the PUT command will\n" --" be used.\n" --"\n" --, stdout); -- fputs( --" Use the file name \"-\" (a single dash) to use stdin instead of a\n" --" given file. Alternately, the file name \".\" (a single period)\n" --" may be specified instead of \"-\" to use stdin in non-blocking\n" --" mode to allow reading server output while stdin is being\n" --" uploaded.\n" --"\n" --" You can specify one -T for each URL on the command line. Each -T\n" --, stdout); -- fputs( --" + URL pair specifies what to upload and to where. curl also sup-\n" --" ports \"globbing\" of the -T argument, meaning that you can upload\n" --" multiple files to a single URL by using the same URL globbing\n" --" style supported in the URL, like this:\n" --"\n" --" curl -T \"{file1,file2}\" http://www.uploadtothissite.com\n" --"\n" --" or even\n" --"\n" --" curl -T \"img[1-1000].png\" ftp://ftp.picturemania.com/upload/\n" --"\n" --" --tcp-nodelay\n" --, stdout); -- fputs( --" Turn on the TCP_NODELAY option. See the curl_easy_setopt(3) man\n" --" page for details about this option. (Added in 7.11.2)\n" --"\n" --" --tftp-blksize \n" --" (TFTP) Set TFTP BLKSIZE option (must be >512). This is the block\n" --" size that curl will try to use when transferring data to or from\n" --" a TFTP server. By default 512 bytes will be used.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --, stdout); -- fputs( --" (Added in 7.20.0)\n" --"\n" --" --tlsauthtype \n" --" Set TLS authentication type. Currently, the only supported\n" --" option is \"SRP\", for TLS-SRP (RFC 5054). If --tlsuser and\n" --" --tlspassword are specified but --tlsauthtype is not, then this\n" --" option defaults to \"SRP\". (Added in 7.21.4)\n" --"\n" --" --tlspassword \n" --" Set password for use with the TLS authentication method speci-\n" --, stdout); -- fputs( --" fied with --tlsauthtype. Requires that --tlsuser also be set.\n" --" (Added in 7.21.4)\n" --"\n" --" --tlsuser \n" --" Set username for use with the TLS authentication method speci-\n" --" fied with --tlsauthtype. Requires that --tlspassword also be\n" --" set. (Added in 7.21.4)\n" --"\n" --" --tlsv1.0\n" --" (SSL) Forces curl to use TLS version 1.0 when negotiating with a\n" --" remote TLS server. (Added in 7.34.0)\n" --"\n" --" --tlsv1.1\n" --, stdout); -- fputs( --" (SSL) Forces curl to use TLS version 1.1 when negotiating with a\n" --" remote TLS server. (Added in 7.34.0)\n" --"\n" --" --tlsv1.2\n" --" (SSL) Forces curl to use TLS version 1.2 when negotiating with a\n" --" remote TLS server. (Added in 7.34.0)\n" --"\n" --" --tr-encoding\n" --" (HTTP) Request a compressed Transfer-Encoding response using one\n" --" of the algorithms curl supports, and uncompress the data while\n" --" receiving it.\n" --"\n" --, stdout); -- fputs( --" (Added in 7.21.6)\n" --"\n" --" --trace \n" --" Enables a full trace dump of all incoming and outgoing data,\n" --" including descriptive information, to the given output file. Use\n" --" \"-\" as filename to have the output sent to stdout.\n" --"\n" --" This option overrides previous uses of -v, --verbose or --trace-\n" --" ascii.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --trace-ascii \n" --, stdout); -- fputs( --" Enables a full trace dump of all incoming and outgoing data,\n" --" including descriptive information, to the given output file. Use\n" --" \"-\" as filename to have the output sent to stdout.\n" --"\n" --" This is very similar to --trace, but leaves out the hex part and\n" --" only shows the ASCII part of the dump. It makes smaller output\n" --" that might be easier to read for untrained humans.\n" --"\n" --, stdout); -- fputs( --" This option overrides previous uses of -v, --verbose or --trace.\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --trace-time\n" --" Prepends a time stamp to each trace or verbose line that curl\n" --" displays. (Added in 7.14.0)\n" --"\n" --" -u, --user \n" --" Specify the user name, password and optional login options to\n" --, stdout); -- fputs( --" use for server authentication. Overrides -n, --netrc and\n" --" --netrc-optional.\n" --"\n" --" If you simply specify the user name, with or without the login\n" --" options, curl will prompt for a password.\n" --"\n" --" If you use an SSPI-enabled curl binary and perform NTLM authen-\n" --" tication, you can force curl to select the user name and pass-\n" --" word from your environment by simply specifying a single colon\n" --, stdout); -- fputs( --" with this option: \"-u :\" or by specifying the login options on\n" --" their own, for example \"-u ;auth=NTLM\".\n" --"\n" --" You can use the optional login options part to specify protocol\n" --" specific options that may be used during authentication. At\n" --" present only IMAP, POP3 and SMTP support login options as part\n" --" of the user login information. For more information about the\n" --, stdout); -- fputs( --" login options please see RFC 2384, RFC 5092 and IETF draft\n" --" draft-earhart-url-smtp-00.txt (Added in 7.31.0).\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -U, --proxy-user \n" --" Specify the user name and password to use for proxy authentica-\n" --" tion.\n" --"\n" --" If you use an SSPI-enabled curl binary and do NTLM authentica-\n" --, stdout); -- fputs( --" tion, you can force curl to pick up the user name and password\n" --" from your environment by simply specifying a single colon with\n" --" this option: \"-U :\".\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --url \n" --" Specify a URL to fetch. This option is mostly handy when you\n" --" want to specify URL(s) in a config file.\n" --"\n" --, stdout); -- fputs( --" This option may be used any number of times. To control where\n" --" this URL is written, use the -o, --output or the -O, --remote-\n" --" name options.\n" --" -v, --verbose\n" --" Makes the fetching more verbose/talkative. Mostly useful for\n" --" debugging. A line starting with '>' means \"header data\" sent by\n" --" curl, '<' means \"header data\" received by curl that is hidden in\n" --, stdout); -- fputs( --" normal cases, and a line starting with '*' means additional info\n" --" provided by curl.\n" --"\n" --" Note that if you only want HTTP headers in the output, -i,\n" --" --include might be the option you're looking for.\n" --"\n" --" If you think this option still doesn't give you enough details,\n" --" consider using --trace or --trace-ascii instead.\n" --"\n" --" This option overrides previous uses of --trace-ascii or --trace.\n" --"\n" --, stdout); -- fputs( --" Use -s, --silent to make curl quiet.\n" --"\n" --" -w, --write-out \n" --" Defines what to display on stdout after a completed and success-\n" --" ful operation. The format is a string that may contain plain\n" --" text mixed with any number of variables. The string can be spec-\n" --" ified as \"string\", to get read from a particular file you spec-\n" --" ify it \"@filename\" and to tell curl to read the format from\n" --, stdout); -- fputs( --" stdin you write \"@-\".\n" --"\n" --" The variables present in the output format will be substituted\n" --" by the value or text that curl thinks fit, as described below.\n" --" All variables are specified as %{variable_name} and to output a\n" --" normal % you just write them as %%. You can output a newline by\n" --" using \\n, a carriage return with \\r and a tab space with \\t.\n" --"\n" --, stdout); -- fputs( --" NOTE: The %-symbol is a special symbol in the win32-environment,\n" --" where all occurrences of % must be doubled when using this\n" --" option.\n" --"\n" --" The variables available are:\n" --"\n" --" content_type The Content-Type of the requested document, if\n" --" there was any.\n" --"\n" --" filename_effective\n" --" The ultimate filename that curl writes out to.\n" --, stdout); -- fputs( --" This is only meaningful if curl is told to write\n" --" to a file with the --remote-name or --output\n" --" option. It's most useful in combination with the\n" --" --remote-header-name option. (Added in 7.25.1)\n" --"\n" --" ftp_entry_path The initial path curl ended up in when logging on\n" --" to the remote FTP server. (Added in 7.15.4)\n" --"\n" --, stdout); -- fputs( --" http_code The numerical response code that was found in the\n" --" last retrieved HTTP(S) or FTP(s) transfer. In\n" --" 7.18.2 the alias response_code was added to show\n" --" the same info.\n" --"\n" --" http_connect The numerical code that was found in the last\n" --" response (from a proxy) to a curl CONNECT\n" --" request. (Added in 7.12.4)\n" --"\n" --, stdout); -- fputs( --" local_ip The IP address of the local end of the most\n" --" recently done connection - can be either IPv4 or\n" --" IPv6 (Added in 7.29.0)\n" --"\n" --" local_port The local port number of the most recently done\n" --" connection (Added in 7.29.0)\n" --"\n" --" num_connects Number of new connects made in the recent trans-\n" --" fer. (Added in 7.12.3)\n" --"\n" --, stdout); -- fputs( --" num_redirects Number of redirects that were followed in the\n" --" request. (Added in 7.12.3)\n" --"\n" --" redirect_url When an HTTP request was made without -L to fol-\n" --" low redirects, this variable will show the actual\n" --" URL a redirect would take you to. (Added in\n" --" 7.18.2)\n" --"\n" --" remote_ip The remote IP address of the most recently done\n" --, stdout); -- fputs( --" connection - can be either IPv4 or IPv6 (Added in\n" --" 7.29.0)\n" --"\n" --" remote_port The remote port number of the most recently done\n" --" connection (Added in 7.29.0)\n" --"\n" --" size_download The total amount of bytes that were downloaded.\n" --"\n" --" size_header The total amount of bytes of the downloaded head-\n" --" ers.\n" --"\n" --, stdout); -- fputs( --" size_request The total amount of bytes that were sent in the\n" --" HTTP request.\n" --"\n" --" size_upload The total amount of bytes that were uploaded.\n" --"\n" --" speed_download The average download speed that curl measured for\n" --" the complete download. Bytes per second.\n" --"\n" --" speed_upload The average upload speed that curl measured for\n" --" the complete upload. Bytes per second.\n" --"\n" --, stdout); -- fputs( --" ssl_verify_result\n" --" The result of the SSL peer certificate verifica-\n" --" tion that was requested. 0 means the verification\n" --" was successful. (Added in 7.19.0)\n" --"\n" --" time_appconnect\n" --" The time, in seconds, it took from the start\n" --" until the SSL/SSH/etc connect/handshake to the\n" --, stdout); -- fputs( --" remote host was completed. (Added in 7.19.0)\n" --"\n" --" time_connect The time, in seconds, it took from the start\n" --" until the TCP connect to the remote host (or\n" --" proxy) was completed.\n" --"\n" --" time_namelookup\n" --" The time, in seconds, it took from the start\n" --" until the name resolving was completed.\n" --"\n" --" time_pretransfer\n" --, stdout); -- fputs( --" The time, in seconds, it took from the start\n" --" until the file transfer was just about to begin.\n" --" This includes all pre-transfer commands and nego-\n" --" tiations that are specific to the particular pro-\n" --" tocol(s) involved.\n" --"\n" --" time_redirect The time, in seconds, it took for all redirection\n" --, stdout); -- fputs( --" steps include name lookup, connect, pretransfer\n" --" and transfer before the final transaction was\n" --" started. time_redirect shows the complete execu-\n" --" tion time for multiple redirections. (Added in\n" --" 7.12.3)\n" --"\n" --" time_starttransfer\n" --" The time, in seconds, it took from the start\n" --, stdout); -- fputs( --" until the first byte was just about to be trans-\n" --" ferred. This includes time_pretransfer and also\n" --" the time the server needed to calculate the\n" --" result.\n" --"\n" --" time_total The total time, in seconds, that the full opera-\n" --" tion lasted. The time will be displayed with mil-\n" --" lisecond resolution.\n" --"\n" --, stdout); -- fputs( --" url_effective The URL that was fetched last. This is most mean-\n" --" ingful if you've told curl to follow location:\n" --" headers.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -x, --proxy <[protocol://][user:password@]proxyhost[:port]>\n" --" Use the specified proxy.\n" --"\n" --" The proxy string can be specified with a protocol:// prefix to\n" --, stdout); -- fputs( --" specify alternative proxy protocols. Use socks4://, socks4a://,\n" --" socks5:// or socks5h:// to request the specific SOCKS version to\n" --" be used. No protocol specified, http:// and all others will be\n" --" treated as HTTP proxies. (The protocol support was added in curl\n" --" 7.21.7)\n" --"\n" --" If the port number is not specified in the proxy string, it is\n" --" assumed to be 1080.\n" --"\n" --, stdout); -- fputs( --" This option overrides existing environment variables that set\n" --" the proxy to use. If there's an environment variable setting a\n" --" proxy, you can set proxy to \"\" to override it.\n" --"\n" --" All operations that are performed over an HTTP proxy will trans-\n" --" parently be converted to HTTP. It means that certain protocol\n" --" specific operations might not be available. This is not the case\n" --, stdout); -- fputs( --" if you can tunnel through the proxy, as one with the -p, --prox-\n" --" ytunnel option.\n" --"\n" --" User and password that might be provided in the proxy string are\n" --" URL decoded by curl. This allows you to pass in special charac-\n" --" ters such as @ by using %40 or pass in a colon with %3a.\n" --"\n" --" The proxy host can be specified the exact same way as the proxy\n" --" environment variables, including the protocol prefix (http://)\n" --, stdout); -- fputs( --" and the embedded user + password.\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" -X, --request \n" --" (HTTP) Specifies a custom request method to use when communicat-\n" --" ing with the HTTP server. The specified request will be used\n" --" instead of the method otherwise used (which defaults to GET).\n" --" Read the HTTP 1.1 specification for details and explanations.\n" --, stdout); -- fputs( --" Common additional HTTP requests include PUT and DELETE, but\n" --" related technologies like WebDAV offers PROPFIND, COPY, MOVE and\n" --" more.\n" --"\n" --" Normally you don't need this option. All sorts of GET, HEAD,\n" --" POST and PUT requests are rather invoked by using dedicated com-\n" --" mand line options.\n" --"\n" --" This option only changes the actual word used in the HTTP\n" --, stdout); -- fputs( --" request, it does not alter the way curl behaves. So for example\n" --" if you want to make a proper HEAD request, using -X HEAD will\n" --" not suffice. You need to use the -I, --head option.\n" --"\n" --" (FTP) Specifies a custom FTP command to use instead of LIST when\n" --" doing file lists with FTP.\n" --"\n" --" (POP3) Specifies a custom POP3 command to use instead of LIST or\n" --" RETR. (Added in 7.26.0)\n" --"\n" --, stdout); -- fputs( --" (IMAP) Specifies a custom IMAP command to use instead of LIST.\n" --" (Added in 7.30.0)\n" --"\n" --" (SMTP) Specifies a custom SMTP command to use instead of HELP or\n" --" VRFY. (Added in 7.34.0)\n" --"\n" --" If this option is used several times, the last one will be used.\n" --"\n" --" --xattr\n" --" When saving output to a file, this option tells curl to store\n" --" certain file metadata in extended file attributes. Currently,\n" --, stdout); -- fputs( --" the URL is stored in the xdg.origin.url attribute and, for HTTP,\n" --" the content type is stored in the mime_type attribute. If the\n" --" file system does not support extended attributes, a warning is\n" --" issued.\n" --"\n" --" -y, --speed-time