From 706f5e1a5d58aef35db6a6007335b2f7edc0bc1d Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 30 Nov 2000 07:55:30 +0000 Subject: README.curl is renamed to MANUAL --- docs/MANUAL | 739 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 739 insertions(+) create mode 100644 docs/MANUAL (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL new file mode 100644 index 000000000..ffd9fb0b6 --- /dev/null +++ b/docs/MANUAL @@ -0,0 +1,739 @@ +LATEST VERSION + + You always find news about what's going on as well as the latest versions + from the curl web pages, located at: + + http://curl.haxx.se + +SIMPLE USAGE + + Get the main page from netscape's web-server: + + curl http://www.netscape.com/ + + Get the root README file from funet's ftp-server: + + curl ftp://ftp.funet.fi/README + + Get a gopher document from funet's gopher server: + + curl gopher://gopher.funet.fi + + Get a web page from a server using port 8000: + + curl http://www.weirdserver.com:8000/ + + Get a list of the root directory of an FTP site: + + curl ftp://ftp.fts.frontec.se/ + + Get the definition of curl from a dictionary: + + curl dict://dict.org/m:curl + +DOWNLOAD TO A FILE + + Get a web page and store in a local file: + + curl -o thatpage.html http://www.netscape.com/ + + Get a web page and store in a local file, make the local file get the name + of the remote document (if no file name part is specified in the URL, this + will fail): + + curl -O http://www.netscape.com/index.html + +USING PASSWORDS + + FTP + + To ftp files using name+passwd, include them in the URL like: + + curl ftp://name:passwd@machine.domain:port/full/path/to/file + + or specify them with the -u flag like + + curl -u name:passwd ftp://machine.domain:port/full/path/to/file + + HTTP + + The HTTP URL doesn't support user and password in the URL string. Curl + does support that anyway to provide a ftp-style interface and thus you can + pick a file like: + + curl http://name:passwd@machine.domain/full/path/to/file + + or specify user and password separately like in + + curl -u name:passwd http://machine.domain/full/path/to/file + + NOTE! Since HTTP URLs don't support user and password, you can't use that + style when using Curl via a proxy. You _must_ use the -u style fetch + during such circumstances. + + HTTPS + + Probably most commonly used with private certificates, as explained below. + + GOPHER + + Curl features no password support for gopher. + +PROXY + + Get an ftp file using a proxy named my-proxy that uses port 888: + + curl -x my-proxy:888 ftp://ftp.leachsite.com/README + + Get a file from a HTTP server that requires user and password, using the + same proxy as above: + + curl -u user:passwd -x my-proxy:888 http://www.get.this/ + + Some proxies require special authentication. Specify by using -U as above: + + curl -U user:passwd -x my-proxy:888 http://www.get.this/ + + See also the environment variables Curl support that offer further proxy + control. + +RANGES + + With HTTP 1.1 byte-ranges were introduced. Using this, a client can request + to get only one or more subparts of a specified document. Curl supports + this with the -r flag. + + Get the first 100 bytes of a document: + + curl -r 0-99 http://www.get.this/ + + Get the last 500 bytes of a document: + + curl -r -500 http://www.get.this/ + + Curl also supports simple ranges for FTP files as well. Then you can only + specify start and stop position. + + Get the first 100 bytes of a document using FTP: + + curl -r 0-99 ftp://www.get.this/README + +UPLOADING + + FTP + + Upload all data on stdin to a specified ftp site: + + curl -t ftp://ftp.upload.com/myfile + + Upload data from a specified file, login with user and password: + + curl -T uploadfile -u user:passwd ftp://ftp.upload.com/myfile + + Upload a local file to the remote site, and use the local file name remote + too: + + curl -T uploadfile -u user:passwd ftp://ftp.upload.com/ + + Upload a local file to get appended to the remote file using ftp: + + curl -T localfile -a ftp://ftp.upload.com/remotefile + + Curl also supports ftp upload through a proxy, but only if the proxy is + configured to allow that kind of tunneling. If it does, you can run curl in + a fashion similar to: + + curl --proxytunnel -x proxy:port -T localfile ftp.upload.com + + HTTP + + Upload all data on stdin to a specified http site: + + curl -t http://www.upload.com/myfile + + Note that the http server must've been configured to accept PUT before this + can be done successfully. + + For other ways to do http data upload, see the POST section below. + +VERBOSE / DEBUG + + If curl fails where it isn't supposed to, if the servers don't let you + in, if you can't understand the responses: use the -v flag to get VERBOSE + fetching. Curl will output lots of info and all data it sends and + receives in order to let the user see all client-server interaction. + + curl -v ftp://ftp.upload.com/ + +DETAILED INFORMATION + + Different protocols provide different ways of getting detailed information + about specific files/documents. To get curl to show detailed information + about a single file, you should use -I/--head option. It displays all + available info on a single file for HTTP and FTP. The HTTP information is a + lot more extensive. + + For HTTP, you can get the header information (the same as -I would show) + shown before the data by using -i/--include. Curl understands the + -D/--dump-header option when getting files from both FTP and HTTP, and it + will then store the headers in the specified file. + + Store the HTTP headers in a separate file: + + curl --dump-header headers.txt curl.haxx.se + + Note that headers stored in a separate file can be very useful at a later + time if you want curl to use cookies sent by the server. More about that in + the cookies section. + +POST (HTTP) + + It's easy to post data using curl. This is done using the -d + option. The post data must be urlencoded. + + Post a simple "name" and "phone" guestbook. + + curl -d "name=Rafael%20Sagula&phone=3320780" \ + http://www.where.com/guest.cgi + + How to post a form with curl, lesson #1: + + Dig out all the tags in the form that you want to fill in. (There's + a perl program called formfind.pl on the curl site that helps with this). + + If there's a "normal" post, you use -d to post. -d takes a full "post + string", which is in the format + + =&=&... + + The 'variable' names are the names set with "name=" in the tags, and + the data is the contents you want to fill in for the inputs. The data *must* + be properly URL encoded. That means you replace space with + and that you + write weird letters with %XX where XX is the hexadecimal representation of + the letter's ASCII code. + + Example: + + (page located at http://www.formpost.com/getthis/ + +
+ + + + +
+ + We want to enter user 'foobar' with password '12345'. + + To post to this, you enter a curl command line like: + + curl -d "user=foobar&pass=12345&id=blablabla&dig=submit" (continues) + http://www.formpost.com/getthis/post.cgi + + + While -d uses the application/x-www-form-urlencoded mime-type, generally + understood by CGI's and similar, curl also supports the more capable + multipart/form-data type. This latter type supports things like file upload. + + -F accepts parameters like -F "name=contents". If you want the contents to + be read from a file, use <@filename> as contents. When specifying a file, + you can also specify which content type the file is, by appending + ';type=' to the file name. You can also post contents of several + files in one field. So that the field name 'coolfiles' can be sent three + files with different content types in a manner similar to: + + curl -F "coolfiles=@fil1.gif;type=image/gif,fil2.txt,fil3.html" \ + http://www.post.com/postit.cgi + + If content-type is not specified, curl will try to guess from the extension + (it only knows a few), or use the previously specified type (from an earlier + file if several files are specified in a list) or finally using the default + type 'text/plain'. + + Emulate a fill-in form with -F. Let's say you fill in three fields in a + form. One field is a file name which to post, one field is your name and one + field is a file description. We want to post the file we have written named + "cooltext.txt". To let curl do the posting of this data instead of your + favourite browser, you have to check out the HTML of the form page to get to + know the names of the input fields. In our example, the input field names are + 'file', 'yourname' and 'filedescription'. + + curl -F "file=@cooltext.txt" -F "yourname=Daniel" \ + -F "filedescription=Cool text file with cool text inside" \ + http://www.post.com/postit.cgi + + So, to send two files in one post you can do it in two ways: + + 1. Send multiple files in a single "field" with a single field name: + + curl -F "pictures=@dog.gif,cat.gif" + + 2. Send two fields with two field names: + + curl -F "docpicture=@dog.gif" -F "catpicture=@cat.gif" + +REFERER + + A HTTP request has the option to include information about which address + that referred to actual page, and curl allows the user to specify that + referrer to get specified on the command line. It is especially useful to + fool or trick stupid servers or CGI scripts that rely on that information + being available or contain certain data. + + curl -e www.coolsite.com http://www.showme.com/ + +USER AGENT + + A HTTP request has the option to include information about the browser + that generated the request. Curl allows it to be specified on the command + line. It is especially useful to fool or trick stupid servers or CGI + scripts that only accept certain browsers. + + Example: + + curl -A 'Mozilla/3.0 (Win95; I)' http://www.nationsbank.com/ + + Other common strings: + 'Mozilla/3.0 (Win95; I)' Netscape Version 3 for Windows 95 + 'Mozilla/3.04 (Win95; U)' Netscape Version 3 for Windows 95 + 'Mozilla/2.02 (OS/2; U)' Netscape Version 2 for OS/2 + 'Mozilla/4.04 [en] (X11; U; AIX 4.2; Nav)' NS for AIX + 'Mozilla/4.05 [en] (X11; U; Linux 2.0.32 i586)' NS for Linux + + Note that Internet Explorer tries hard to be compatible in every way: + 'Mozilla/4.0 (compatible; MSIE 4.01; Windows 95)' MSIE for W95 + + Mozilla is not the only possible User-Agent name: + 'Konqueror/1.0' KDE File Manager desktop client + 'Lynx/2.7.1 libwww-FM/2.14' Lynx command line browser + +COOKIES + + Cookies are generally used by web servers to keep state information at the + client's side. The server sets cookies by sending a response line in the + headers that looks like 'Set-Cookie: ' where the data part then + typically contains a set of NAME=VALUE pairs (separated by semicolons ';' + like "NAME1=VALUE1; NAME2=VALUE2;"). The server can also specify for what + path the "cookie" should be used for (by specifying "path=value"), when the + cookie should expire ("expire=DATE"), for what domain to use it + ("domain=NAME") and if it should be used on secure connections only + ("secure"). + + If you've received a page from a server that contains a header like: + Set-Cookie: sessionid=boo123; path="/foo"; + + it means the server wants that first pair passed on when we get anything in + a path beginning with "/foo". + + Example, get a page that wants my name passed in a cookie: + + curl -b "name=Daniel" www.sillypage.com + + Curl also has the ability to use previously received cookies in following + sessions. If you get cookies from a server and store them in a file in a + manner similar to: + + curl --dump-header headers www.example.com + + ... you can then in a second connect to that (or another) site, use the + cookies from the 'headers' file like: + + curl -b headers www.example.com + + Note that by specifying -b you enable the "cookie awareness" and with -L + you can make curl follow a location: (which often is used in combination + with cookies). So that if a site sends cookies and a location, you can + use a non-existing file to trig the cookie awareness like: + + curl -L -b empty-file www.example.com + + The file to read cookies from must be formatted using plain HTTP headers OR + as netscape's cookie file. Curl will determine what kind it is based on the + file contents. + +PROGRESS METER + + The progress meter exists to show a user that something actually is + happening. The different fields in the output have the following meaning: + + % Total % Received % Xferd Average Speed Time Curr. + Dload Upload Total Current Left Speed + 0 151M 0 38608 0 0 9406 0 4:41:43 0:00:04 4:41:39 9287 + + From left-to-right: + % - percentage completed of the whole transfer + Total - total size of the whole expected transfer + % - percentage completed of the download + Received - currently downloaded amount of bytes + % - percentage completed of the upload + Xferd - currently uploaded amount of bytes + Average Speed + Dload - the average transfer speed of the download + Average Speed + Upload - the average transfer speed of the upload + Time Total - expected time to complete the operation + Time Current - time passed since the invoke + Time Left - expected time left to completetion + Curr.Speed - the average transfer speed the last 5 seconds (the first + 5 seconds of a transfer is based on less time of course.) + + The -# option will display a totally different progress bar that doesn't + need much explanation! + +SPEED LIMIT + + Curl offers the user to set conditions regarding transfer speed that must + be met to let the transfer keep going. By using the switch -y and -Y you + can make curl abort transfers if the transfer speed doesn't exceed your + given lowest limit for a specified time. + + To let curl abandon downloading this page if its slower than 3000 bytes per + second for 1 minute, run: + + curl -y 3000 -Y 60 www.far-away-site.com + + This can very well be used in combination with the overall time limit, so + that the above operatioin must be completed in whole within 30 minutes: + + curl -m 1800 -y 3000 -Y 60 www.far-away-site.com + +CONFIG FILE + + Curl automatically tries to read the .curlrc file (or _curlrc file on win32 + systems) from the user's home dir on startup. + + The config file could be made up with normal command line switches, but you + can also specify the long options without the dashes to make it more + readable. You can separate the options and the parameter with spaces, or + with = or :. Comments can be used within the file. If the first letter on a + line is a '#'-letter the rest of the line is treated as a comment. + + If you want the parameter to contain spaces, you must inclose the entire + parameter within double quotes ("). Within those quotes, you specify a + quote as \". + + NOTE: You must specify options and their arguments on the same line. + + Example, set default time out and proxy in a config file: + + # We want a 30 minute timeout: + -m 1800 + # ... and we use a proxy for all accesses: + proxy = proxy.our.domain.com:8080 + + White spaces ARE significant at the end of lines, but all white spaces + leading up to the first characters of each line are ignored. + + Prevent curl from reading the default file by using -q as the first command + line parameter, like: + + curl -q www.thatsite.com + + Force curl to get and display a local help page in case it is invoked + without URL by making a config file similar to: + + # default url to get + url = "http://help.with.curl.com/curlhelp.html" + + You can specify another config file to be read by using the -K/--config + flag. If you set config file name to "-" it'll read the config from stdin, + which can be handy if you want to hide options from being visible in process + tables etc: + + echo "user = user:passwd" | curl -K - http://that.secret.site.com + +EXTRA HEADERS + + When using curl in your own very special programs, you may end up needing + to pass on your own custom headers when getting a web page. You can do + this by using the -H flag. + + Example, send the header "X-you-and-me: yes" to the server when getting a + page: + + curl -H "X-you-and-me: yes" www.love.com + + This can also be useful in case you want curl to send a different text in + a header than it normally does. The -H header you specify then replaces the + header curl would normally send. + +FTP and PATH NAMES + + Do note that when getting files with the ftp:// URL, the given path is + relative the directory you enter. To get the file 'README' from your home + directory at your ftp site, do: + + curl ftp://user:passwd@my.site.com/README + + But if you want the README file from the root directory of that very same + site, you need to specify the absolute file name: + + curl ftp://user:passwd@my.site.com//README + + (I.e with an extra slash in front of the file name.) + +FTP and firewalls + + The FTP protocol requires one of the involved parties to open a second + connction as soon as data is about to get transfered. There are two ways to + do this. + + The default way for curl is to issue the PASV command which causes the + server to open another port and await another connection performed by the + client. This is good if the client is behind a firewall that don't allow + incoming connections. + + curl ftp.download.com + + If the server for example, is behind a firewall that don't allow connections + on other ports than 21 (or if it just doesn't support the PASV command), the + other way to do it is to use the PORT command and instruct the server to + connect to the client on the given (as parameters to the PORT command) IP + number and port. + + The -P flag to curl supports a few different options. Your machine may have + several IP-addresses and/or network interfaces and curl allows you to select + which of them to use. Default address can also be used: + + curl -P - ftp.download.com + + Download with PORT but use the IP address of our 'le0' interface (this does + not work on windows): + + curl -P le0 ftp.download.com + + Download with PORT but use 192.168.0.10 as our IP address to use: + + curl -P 192.168.0.10 ftp.download.com + +NETWORK INTERFACE + + Get a web page from a server using a specified port for the interface: + + curl --interface eth0:1 http://www.netscape.com/ + + or + + curl --interface 192.168.1.10 http://www.netscape.com/ + +HTTPS + + Secure HTTP requires SSL libraries to be installed and used when curl is + built. If that is done, curl is capable of retrieving and posting documents + using the HTTPS procotol. + + Example: + + curl https://www.secure-site.com + + Curl is also capable of using your personal certificates to get/post files + from sites that require valid certificates. The only drawback is that the + certificate needs to be in PEM-format. PEM is a standard and open format to + store certificates with, but it is not used by the most commonly used + browsers (Netscape and MSEI both use the so called PKCS#12 format). If you + want curl to use the certificates you use with your (favourite) browser, you + may need to download/compile a converter that can convert your browser's + formatted certificates to PEM formatted ones. This kind of converter is + included in recent versions of OpenSSL, and for older versions Dr Stephen + N. Henson has written a patch for SSLeay that adds this functionality. You + can get his patch (that requires an SSLeay installation) from his site at: + http://www.drh-consultancy.demon.co.uk/ + + Example on how to automatically retrieve a document using a certificate with + a personal password: + + curl -E /path/to/cert.pem:password https://secure.site.com/ + + If you neglect to specify the password on the command line, you will be + prompted for the correct password before any data can be received. + + Many older SSL-servers have problems with SSLv3 or TLS, that newer versions + of OpenSSL etc is using, therefore it is sometimes useful to specify what + SSL-version curl should use. Use -3 or -2 to specify that exact SSL version + to use: + + curl -2 https://secure.site.com/ + + Otherwise, curl will first attempt to use v3 and then v2. + + To use OpenSSL to convert your favourite browser's certificate into a PEM + formatted one that curl can use, do something like this (assuming netscape, + but IE is likely to work similarly): + + You start with hitting the 'security' menu button in netscape. + + Select 'certificates->yours' and then pick a certificate in the list + + Press the 'export' button + + enter your PIN code for the certs + + select a proper place to save it + + Run the 'openssl' application to convert the certificate. If you cd to the + openssl installation, you can do it like: + + # ./apps/openssl pkcs12 -certfile [file you saved] -out [PEMfile] + + +RESUMING FILE TRANSFERS + + To continue a file transfer where it was previously aborted, curl supports + resume on http(s) downloads as well as ftp uploads and downloads. + + Continue downloading a document: + + curl -c -o file ftp://ftp.server.com/path/file + + Continue uploading a document(*1): + + curl -c -T file ftp://ftp.server.com/path/file + + Continue downloading a document from a web server(*2): + + curl -c -o file http://www.server.com/ + + (*1) = This requires that the ftp server supports the non-standard command + SIZE. If it doesn't, curl will say so. + + (*2) = This requires that the wb server supports at least HTTP/1.1. If it + doesn't, curl will say so. + +TIME CONDITIONS + + HTTP allows a client to specify a time condition for the document it + requests. It is If-Modified-Since or If-Unmodified-Since. Curl allow you to + specify them with the -z/--time-cond flag. + + For example, you can easily make a download that only gets performed if the + remote file is newer than a local copy. It would be made like: + + curl -z local.html http://remote.server.com/remote.html + + Or you can download a file only if the local file is newer than the remote + one. Do this by prepending the date string with a '-', as in: + + curl -z -local.html http://remote.server.com/remote.html + + You can specify a "free text" date as condition. Tell curl to only download + the file if it was updated since yesterday: + + curl -z yesterday http://remote.server.com/remote.html + + Curl will then accept a wide range of date formats. You always make the date + check the other way around by prepending it with a dash '-'. + +DICT + + For fun try + + curl dict://dict.org/m:curl + curl dict://dict.org/d:heisenbug:jargon + curl dict://dict.org/d:daniel:web1913 + + Aliases for 'm' are 'match' and 'find', and aliases for 'd' are 'define' + and 'lookup'. For example, + + curl dict://dict.org/find:curl + + Commands that break the URL description of the RFC (but not the DICT + protocol) are + + curl dict://dict.org/show:db + curl dict://dict.org/show:strat + + Authentication is still missing (but this is not required by the RFC) + +LDAP + + If you have installed the OpenLDAP library, curl can take advantage of it + and offer ldap:// support. + + LDAP is a complex thing and writing an LDAP query is not an easy task. I do + advice you to dig up the syntax description for that elsewhere, RFC 1959 if + no other place is better. + + To show you an example, this is now I can get all people from my local LDAP + server that has a certain sub-domain in their email address: + + curl -B "ldap://ldap.frontec.se/o=frontec??sub?mail=*sth.frontec.se" + + If I want the same info in HTML format, I can get it by not using the -B + (enforce ASCII) flag. + +ENVIRONMENT VARIABLES + + Curl reads and understands the following environment variables: + + HTTP_PROXY, HTTPS_PROXY, FTP_PROXY, GOPHER_PROXY + + They should be set for protocol-specific proxies. General proxy should be + set with + + ALL_PROXY + + A comma-separated list of host names that shouldn't go through any proxy is + set in (only an asterisk, '*' matches all hosts) + + NO_PROXY + + If a tail substring of the domain-path for a host matches one of these + strings, transactions with that node will not be proxied. + + + The usage of the -x/--proxy flag overrides the environment variables. + +NETRC + + Unix introduced the .netrc concept a long time ago. It is a way for a user + to specify name and password for commonly visited ftp sites in a file so + that you don't have to type them in each time you visit those sites. You + realize this is a big security risk if someone else gets hold of your + passwords, so therefor most unix programs won't read this file unless it is + only readable by yourself (curl doesn't care though). + + Curl supports .netrc files if told so (using the -n/--netrc option). This is + not restricted to only ftp, but curl can use it for all protocols where + authentication is used. + + A very simple .netrc file could look something like: + + machine curl.haxx.se login iamdaniel password mysecret + +CUSTOM OUTPUT + + To better allow script programmers to get to know about the progress of + curl, the -w/--write-out option was introduced. Using this, you can specify + what information from the previous transfer you want to extract. + + To display the amount of bytes downloaded together with some text and an + ending newline: + + curl -w 'We downloaded %{size_download} bytes\n' www.download.com + +KERBEROS4 FTP TRANSFER + + Curl supports kerberos4 for FTP transfers. You need the kerberos package + installed and used at curl build time for it to be used. + + First, get the krb-ticket the normal way, like with the kauth tool. Then use + curl in way similar to: + + curl --krb4 private ftp://krb4site.com -u username:fakepwd + + There's no use for a password on the -u switch, but a blank one will make + curl ask for one and you already entered the real password to kauth. + +MAILING LIST + + We have an open mailing list to discuss curl, its development and things + relevant to this. + + To subscribe, mail curl-request@contactor.se with "subscribe " in the body. + + To post to the list, mail curl@contactor.se. + + To unsubcribe, mail curl-request@contactor.se with "unsubscribe " in the body. + -- cgit v1.2.1 From ea3b6914cc4f8a28861dd34c84992ff8222bed29 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 30 Nov 2000 08:08:23 +0000 Subject: Added a small note about referer needing to be complete to comply to the HTTP spec --- docs/MANUAL | 2 ++ 1 file changed, 2 insertions(+) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index ffd9fb0b6..d1c67442d 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -282,6 +282,8 @@ REFERER curl -e www.coolsite.com http://www.showme.com/ + NOTE: The referer field is defined in the HTTP spec to be a full URL. + USER AGENT A HTTP request has the option to include information about the browser -- cgit v1.2.1 From c6355e6a43c25180aaa7c78a64e1123a4775d7c8 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 5 Feb 2001 22:35:21 +0000 Subject: Added a telnet section --- docs/MANUAL | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index d1c67442d..356cb186d 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -726,6 +726,26 @@ KERBEROS4 FTP TRANSFER There's no use for a password on the -u switch, but a blank one will make curl ask for one and you already entered the real password to kauth. +TELNET + + The curl telnet support is basic and very easy to use. Curl passes all data + passed to it on stdin to the remote server. Connect to a remote telnet + server using a command line similar to: + + curl telnet://remote.server.com + + And enter the data to pass to the server on stdin. The result will be sent + stdout or to the file you specify with -o. + + You might want the -N/--no-buffer option to switch off the buffered output + for slow connections or if the output from the remote site is slow and/or + without newlines. + + NOTE: the telnet protocol does not specify any way to login with a specified + user and password and thus curl can't do that automatically. To do that, you + need to track when the login prompt is received and send the username and + password accordingly. + MAILING LIST We have an open mailing list to discuss curl, its development and things -- cgit v1.2.1 From 61e2a8108b604b55bc88e741ad6378827c926ade Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 7 Feb 2001 09:49:06 +0000 Subject: 7.6.1-pre3 --- docs/MANUAL | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 356cb186d..5f7051e6a 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -735,15 +735,14 @@ TELNET curl telnet://remote.server.com And enter the data to pass to the server on stdin. The result will be sent - stdout or to the file you specify with -o. + to stdout or to the file you specify with -o. You might want the -N/--no-buffer option to switch off the buffered output - for slow connections or if the output from the remote site is slow and/or - without newlines. + for slow connections or similar. NOTE: the telnet protocol does not specify any way to login with a specified - user and password and thus curl can't do that automatically. To do that, you - need to track when the login prompt is received and send the username and + user and password so curl can't do that automatically. To do that, you need + to track when the login prompt is received and send the username and password accordingly. MAILING LIST -- cgit v1.2.1 From 42e4f9d77682f5b43891de78ce39673b0331fcd8 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 19 Feb 2001 09:25:18 +0000 Subject: added stuff to the mailing list chapter --- docs/MANUAL | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 5f7051e6a..63f5d2616 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -745,16 +745,22 @@ TELNET to track when the login prompt is received and send the username and password accordingly. -MAILING LIST +MAILING LISTS - We have an open mailing list to discuss curl, its development and things - relevant to this. + For your convenience, we have several open mailing lists to discuss curl, + its development and things relevant to this. - To subscribe, mail curl-request@contactor.se with "subscribe " in the body. + To subscribe to the main curl list, mail curl-request@contactor.se with + "subscribe " in the body. - To post to the list, mail curl@contactor.se. + To subscribe to the libcurl users list, follow the instructions at + http://curl.haxx.se/mail/ - To unsubcribe, mail curl-request@contactor.se with "unsubscribe " in the body. + To subscribe to the curl announce list, to only get information about new + releases, follow the instructions at http://curl.haxx.se/mail/ + To subscribe to the curl-and-PHP list in which curl using with PHP is + discussed, follow the instructions at http://curl.haxx.se/mail/ + + Please direct curl questions, feature requests and trouble reports to one of + these mailing lists instead of mailing any individual. -- cgit v1.2.1 From a4af638867a984ae748e33ed204f9486f5430abf Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 12 Mar 2001 09:44:08 +0000 Subject: added persistant connection details --- docs/MANUAL | 44 +++++++++++++++++++++++++++++++++++++------- 1 file changed, 37 insertions(+), 7 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 63f5d2616..843b0bd2d 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -25,12 +25,16 @@ SIMPLE USAGE Get a list of the root directory of an FTP site: - curl ftp://ftp.fts.frontec.se/ + curl ftp://cool.haxx.se/ Get the definition of curl from a dictionary: curl dict://dict.org/m:curl + Fetch two documents at once: + + curl ftp://cool.haxx.se/ http://www.weirdserver.com:8000/ + DOWNLOAD TO A FILE Get a web page and store in a local file: @@ -43,6 +47,10 @@ DOWNLOAD TO A FILE curl -O http://www.netscape.com/index.html + Fetch two files and store them with their remote names: + + curl -O www.haxx.se/index.html -O curl.haxx.se/download.html + USING PASSWORDS FTP @@ -455,9 +463,13 @@ EXTRA HEADERS curl -H "X-you-and-me: yes" www.love.com - This can also be useful in case you want curl to send a different text in - a header than it normally does. The -H header you specify then replaces the - header curl would normally send. + This can also be useful in case you want curl to send a different text in a + header than it normally does. The -H header you specify then replaces the + header curl would normally send. If you replace an internal header with an + empty one, you prevent that header from being sent. To prevent the Host: + header from being used: + + curl -H "Host:" www.server.com FTP and PATH NAMES @@ -745,6 +757,24 @@ TELNET to track when the login prompt is received and send the username and password accordingly. +PERSISTANT CONNECTIONS + + Specifying multiple files on a single command line will make curl transfer + all of them, one after the other in the specified order. + + libcurl will attempt to use persistant connections for the transfers so that + the second transfer to the same host can use the same connection that was + already initiated and was left open in the previous transfer. This greatly + decreases connection time for all but the first transfer and it makes a far + better use of the network. + + Note that curl cannot use persistant connections for transfers that are used + in subsequence curl invokes. Try to stuff as many URLs as possible on the + same command line if they are using the same host, as that'll make the + transfers faster. + + Persistant connections were introduced in curl 7.7. + MAILING LISTS For your convenience, we have several open mailing lists to discuss curl, @@ -753,10 +783,10 @@ MAILING LISTS To subscribe to the main curl list, mail curl-request@contactor.se with "subscribe " in the body. - To subscribe to the libcurl users list, follow the instructions at - http://curl.haxx.se/mail/ + To subscribe to the curl-library users/deverlopers list, follow the + instructions at http://curl.haxx.se/mail/ - To subscribe to the curl announce list, to only get information about new + To subscribe to the curl-announce list, to only get information about new releases, follow the instructions at http://curl.haxx.se/mail/ To subscribe to the curl-and-PHP list in which curl using with PHP is -- cgit v1.2.1 From 440a3101d00aff2fe1f7a0d1ba95c9ed10d611c7 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 12 Mar 2001 13:54:46 +0000 Subject: added a note about persitant connections through HTTP proxies --- docs/MANUAL | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 843b0bd2d..f7733c6f1 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -771,7 +771,8 @@ PERSISTANT CONNECTIONS Note that curl cannot use persistant connections for transfers that are used in subsequence curl invokes. Try to stuff as many URLs as possible on the same command line if they are using the same host, as that'll make the - transfers faster. + transfers faster. If you use a http proxy for file transfers, practicly + all transfers will be persistant. Persistant connections were introduced in curl 7.7. -- cgit v1.2.1 From bc5954fe2d332e4cd47a0d749b4becc7fd46e4c8 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 23 Mar 2001 08:16:24 +0000 Subject: updates by SM nttp at iname.com --- docs/MANUAL | 60 ++++++++++++++++++++++++++++++++---------------------------- 1 file changed, 32 insertions(+), 28 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index f7733c6f1..de35e1694 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -15,10 +15,6 @@ SIMPLE USAGE curl ftp://ftp.funet.fi/README - Get a gopher document from funet's gopher server: - - curl gopher://gopher.funet.fi - Get a web page from a server using port 8000: curl http://www.weirdserver.com:8000/ @@ -27,6 +23,10 @@ SIMPLE USAGE curl ftp://cool.haxx.se/ + Get a gopher document from funet's gopher server: + + curl gopher://gopher.funet.fi + Get the definition of curl from a dictionary: curl dict://dict.org/m:curl @@ -186,7 +186,7 @@ DETAILED INFORMATION -D/--dump-header option when getting files from both FTP and HTTP, and it will then store the headers in the specified file. - Store the HTTP headers in a separate file: + Store the HTTP headers in a separate file (headers.txt in the example): curl --dump-header headers.txt curl.haxx.se @@ -245,32 +245,32 @@ POST (HTTP) -F accepts parameters like -F "name=contents". If you want the contents to be read from a file, use <@filename> as contents. When specifying a file, - you can also specify which content type the file is, by appending - ';type=' to the file name. You can also post contents of several - files in one field. So that the field name 'coolfiles' can be sent three - files with different content types in a manner similar to: + you can also specify the file content type by appending ';type=' + to the file name. You can also post the contents of several files in one field. + For example, the field name 'coolfiles' is used to send three files, with + different content types using the following syntax: curl -F "coolfiles=@fil1.gif;type=image/gif,fil2.txt,fil3.html" \ http://www.post.com/postit.cgi - If content-type is not specified, curl will try to guess from the extension - (it only knows a few), or use the previously specified type (from an earlier - file if several files are specified in a list) or finally using the default - type 'text/plain'. + If the content-type is not specified, curl will try to guess from the file + extension (it only knows a few), or use the previously specified type + (from an earlier file if several files are specified in a list) or else it + will using the default type 'text/plain'. Emulate a fill-in form with -F. Let's say you fill in three fields in a form. One field is a file name which to post, one field is your name and one field is a file description. We want to post the file we have written named "cooltext.txt". To let curl do the posting of this data instead of your - favourite browser, you have to check out the HTML of the form page to get to - know the names of the input fields. In our example, the input field names are + favourite browser, you have to read the HTML source of the form page and find + the names of the input fields. In our example, the input field names are 'file', 'yourname' and 'filedescription'. curl -F "file=@cooltext.txt" -F "yourname=Daniel" \ -F "filedescription=Cool text file with cool text inside" \ http://www.post.com/postit.cgi - So, to send two files in one post you can do it in two ways: + To send two files in one post you can do it in two ways: 1. Send multiple files in a single "field" with a single field name: @@ -280,11 +280,11 @@ POST (HTTP) curl -F "docpicture=@dog.gif" -F "catpicture=@cat.gif" -REFERER +REFERRER A HTTP request has the option to include information about which address - that referred to actual page, and curl allows the user to specify that - referrer to get specified on the command line. It is especially useful to + that referred to actual page. Curl allows you to specify the + referrer to be used on the command line. It is especially useful to fool or trick stupid servers or CGI scripts that rely on that information being available or contain certain data. @@ -353,13 +353,17 @@ COOKIES Note that by specifying -b you enable the "cookie awareness" and with -L you can make curl follow a location: (which often is used in combination with cookies). So that if a site sends cookies and a location, you can - use a non-existing file to trig the cookie awareness like: + use a non-existing file to trigger the cookie awareness like: - curl -L -b empty-file www.example.com + curl -L -b empty.txt www.example.com The file to read cookies from must be formatted using plain HTTP headers OR as netscape's cookie file. Curl will determine what kind it is based on the - file contents. + file contents. In the above command, curl will parse the header and store + the cookies received from www.example.com. curl will send to the server the + stored cookies which match the request as it follows the location. The + file "empty.txt" may be a non-existant file. + PROGRESS METER @@ -392,12 +396,12 @@ PROGRESS METER SPEED LIMIT - Curl offers the user to set conditions regarding transfer speed that must - be met to let the transfer keep going. By using the switch -y and -Y you - can make curl abort transfers if the transfer speed doesn't exceed your - given lowest limit for a specified time. + Curl allows the user to set the transfer speed conditions that must be met + to let the transfer keep going. By using the switch -y and -Y you + can make curl abort transfers if the transfer speed is below the specified + lowest limit for a specified time. - To let curl abandon downloading this page if its slower than 3000 bytes per + To have curl abort the download if the speed is slower than 3000 bytes per second for 1 minute, run: curl -y 3000 -Y 60 www.far-away-site.com @@ -610,7 +614,7 @@ RESUMING FILE TRANSFERS (*1) = This requires that the ftp server supports the non-standard command SIZE. If it doesn't, curl will say so. - (*2) = This requires that the wb server supports at least HTTP/1.1. If it + (*2) = This requires that the web server supports at least HTTP/1.1. If it doesn't, curl will say so. TIME CONDITIONS -- cgit v1.2.1 From 929366b5aead7301c4872713acb543c73443959f Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 2 Aug 2001 17:12:07 +0000 Subject: Frank Keeney pointed out a manual mistake for certificate convertions --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index de35e1694..cffaad158 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -591,7 +591,7 @@ HTTPS Run the 'openssl' application to convert the certificate. If you cd to the openssl installation, you can do it like: - # ./apps/openssl pkcs12 -certfile [file you saved] -out [PEMfile] + # ./apps/openssl pkcs12 -in [file you saved] -clcerts -out [PEMfile] RESUMING FILE TRANSFERS -- cgit v1.2.1 From bc8375a1e8fe8268de12ab1f821ed4ab6130c154 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 30 Oct 2001 08:09:08 +0000 Subject: removed silly old -t usage from here, added some blurb about the "new" -t that sets telnet options --- docs/MANUAL | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index cffaad158..23e82ff25 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -132,7 +132,7 @@ UPLOADING Upload all data on stdin to a specified ftp site: - curl -t ftp://ftp.upload.com/myfile + curl -T - ftp://ftp.upload.com/myfile Upload data from a specified file, login with user and password: @@ -157,7 +157,7 @@ UPLOADING Upload all data on stdin to a specified http site: - curl -t http://www.upload.com/myfile + curl -T - http://www.upload.com/myfile Note that the http server must've been configured to accept PUT before this can be done successfully. @@ -756,6 +756,17 @@ TELNET You might want the -N/--no-buffer option to switch off the buffered output for slow connections or similar. + Pass options to the telnet protocol negotiation, by using the -t option. To + tell the server we use a vt100 terminal, try something like: + + curl -tTTYPE=vt100 telnet://remote.server.com + + Other interesting options for it -t include: + + - XDISPLOC= Sets the X display location. + + - NEW_ENV= Sets an environment variable. + NOTE: the telnet protocol does not specify any way to login with a specified user and password so curl can't do that automatically. To do that, you need to track when the login prompt is received and send the username and -- cgit v1.2.1 From f1c14fe0b4bdf28088e63db809699c3f751e2759 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 4 Jan 2002 13:15:07 +0000 Subject: The former -c is "-C -" these days --- docs/MANUAL | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 23e82ff25..ede541191 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -601,15 +601,15 @@ RESUMING FILE TRANSFERS Continue downloading a document: - curl -c -o file ftp://ftp.server.com/path/file + curl -C - -o file ftp://ftp.server.com/path/file Continue uploading a document(*1): - curl -c -T file ftp://ftp.server.com/path/file + curl -C - -T file ftp://ftp.server.com/path/file Continue downloading a document from a web server(*2): - curl -c -o file http://www.server.com/ + curl -C - -o file http://www.server.com/ (*1) = This requires that the ftp server supports the non-standard command SIZE. If it doesn't, curl will say so. -- cgit v1.2.1 From 89bad584c38a681642d100c789ba6c3391988237 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 18 Feb 2002 10:47:27 +0000 Subject: updated LDAP URL syntax references by Aron Roberts --- docs/MANUAL | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index ede541191..0af8c8205 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -668,8 +668,14 @@ LDAP and offer ldap:// support. LDAP is a complex thing and writing an LDAP query is not an easy task. I do - advice you to dig up the syntax description for that elsewhere, RFC 1959 if - no other place is better. + advice you to dig up the syntax description for that elsewhere. Two places + that might suit you are: + + Netscape's "Netscape Directory SDK 3.0 for C Programmer's Guide Chapter 10: + Working with LDAP URLs": + http://developer.netscape.com/docs/manuals/dirsdk/csdk30/url.htm + + RFC 2255, "The LDAP URL Format" http://www.rfc-editor.org/rfc/rfc2255.txt To show you an example, this is now I can get all people from my local LDAP server that has a certain sub-domain in their email address: -- cgit v1.2.1 From c2d4fd876c77132caf593e397db615eb12266c7d Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 7 Mar 2002 08:50:18 +0000 Subject: 7.9.5 commit --- docs/MANUAL | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 0af8c8205..8a66d1342 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -246,25 +246,25 @@ POST (HTTP) -F accepts parameters like -F "name=contents". If you want the contents to be read from a file, use <@filename> as contents. When specifying a file, you can also specify the file content type by appending ';type=' - to the file name. You can also post the contents of several files in one field. - For example, the field name 'coolfiles' is used to send three files, with - different content types using the following syntax: + to the file name. You can also post the contents of several files in one + field. For example, the field name 'coolfiles' is used to send three files, + with different content types using the following syntax: curl -F "coolfiles=@fil1.gif;type=image/gif,fil2.txt,fil3.html" \ http://www.post.com/postit.cgi If the content-type is not specified, curl will try to guess from the file - extension (it only knows a few), or use the previously specified type - (from an earlier file if several files are specified in a list) or else it - will using the default type 'text/plain'. + extension (it only knows a few), or use the previously specified type (from + an earlier file if several files are specified in a list) or else it will + using the default type 'text/plain'. Emulate a fill-in form with -F. Let's say you fill in three fields in a form. One field is a file name which to post, one field is your name and one field is a file description. We want to post the file we have written named "cooltext.txt". To let curl do the posting of this data instead of your - favourite browser, you have to read the HTML source of the form page and find - the names of the input fields. In our example, the input field names are - 'file', 'yourname' and 'filedescription'. + favourite browser, you have to read the HTML source of the form page and + find the names of the input fields. In our example, the input field names + are 'file', 'yourname' and 'filedescription'. curl -F "file=@cooltext.txt" -F "yourname=Daniel" \ -F "filedescription=Cool text file with cool text inside" \ -- cgit v1.2.1 From dc3d0289d66429da19172dd4a1341fd2ce60545b Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 20 Mar 2002 08:00:05 +0000 Subject: old list is gone --- docs/MANUAL | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 8a66d1342..da23259fa 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -802,8 +802,8 @@ MAILING LISTS For your convenience, we have several open mailing lists to discuss curl, its development and things relevant to this. - To subscribe to the main curl list, mail curl-request@contactor.se with - "subscribe " in the body. + To subscribe to the curl-users list, follow the the instructions + at http://curl.haxx.se/mail/ To subscribe to the curl-library users/deverlopers list, follow the instructions at http://curl.haxx.se/mail/ -- cgit v1.2.1 From d26c318321d9517b890dbb6ea79aaeb648989ae7 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 12 Apr 2002 10:33:40 +0000 Subject: explain all mailing lists better --- docs/MANUAL | 38 +++++++++++++++++++++++++++++--------- 1 file changed, 29 insertions(+), 9 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index da23259fa..ce63326eb 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -800,19 +800,39 @@ PERSISTANT CONNECTIONS MAILING LISTS For your convenience, we have several open mailing lists to discuss curl, - its development and things relevant to this. + its development and things relevant to this. Get all info at + http://curl.haxx.se/mail/. The lists available are: - To subscribe to the curl-users list, follow the the instructions - at http://curl.haxx.se/mail/ + curl-users - To subscribe to the curl-library users/deverlopers list, follow the - instructions at http://curl.haxx.se/mail/ + Users of the command line tool. How to use it, what doesn't work, new + features, related tools, questions, news, installations, compilations, + running, porting etc. - To subscribe to the curl-announce list, to only get information about new - releases, follow the instructions at http://curl.haxx.se/mail/ + curl-library - To subscribe to the curl-and-PHP list in which curl using with PHP is - discussed, follow the instructions at http://curl.haxx.se/mail/ + Developers using or developing libcurl. Bugs, extensions, improvements. + + curl-announce + + Low-traffic. Only announcements of new public versions. + + curl-and-PHP + + Using the curl functions in PHP. Everything curl with a PHP angle. Or PHP + with a curl angle. + + curl-commits + + Receives notifications on all CVS commits done to the curl source module. + This can become quite a large amount of mails during intense development, + be aware. This is for us who liks email... + + curl-www-commits + + Receives notifications on all CVS commits done to the curl www module + (basicly the web site). This can become quite a large amount of mails + during intense changing, be aware. This is for us who liks email... Please direct curl questions, feature requests and trouble reports to one of these mailing lists instead of mailing any individual. -- cgit v1.2.1 From b00c59816debf160d6d6e97df6cd38217109f3b1 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 12 Apr 2002 14:33:57 +0000 Subject: http_proxy must be lower case --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index ce63326eb..b58c4fb86 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -689,7 +689,7 @@ ENVIRONMENT VARIABLES Curl reads and understands the following environment variables: - HTTP_PROXY, HTTPS_PROXY, FTP_PROXY, GOPHER_PROXY + http_proxy, HTTPS_PROXY, FTP_PROXY, GOPHER_PROXY They should be set for protocol-specific proxies. General proxy should be set with -- cgit v1.2.1 From 51fcee6f811c46c55cefebb726e6c4dee7dedd13 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 21 May 2002 22:20:16 +0000 Subject: James Cone added CURLOPT_NETRC / --netrc / --netrc-optional descriptions --- docs/MANUAL | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index b58c4fb86..e496f0243 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -716,9 +716,9 @@ NETRC passwords, so therefor most unix programs won't read this file unless it is only readable by yourself (curl doesn't care though). - Curl supports .netrc files if told so (using the -n/--netrc option). This is - not restricted to only ftp, but curl can use it for all protocols where - authentication is used. + Curl supports .netrc files if told so (using the -n/--netrc and + --netrc-optional options). This is not restricted to only ftp, + but curl can use it for all protocols where authentication is used. A very simple .netrc file could look something like: -- cgit v1.2.1 From da86e32eb4207887d2d30d395dd721341c1c7930 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sat, 12 Oct 2002 12:14:09 +0000 Subject: -y and -Y was switched in the examples --- docs/MANUAL | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index e496f0243..95211ed63 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -404,12 +404,12 @@ SPEED LIMIT To have curl abort the download if the speed is slower than 3000 bytes per second for 1 minute, run: - curl -y 3000 -Y 60 www.far-away-site.com + curl -Y 3000 -y 60 www.far-away-site.com This can very well be used in combination with the overall time limit, so that the above operatioin must be completed in whole within 30 minutes: - curl -m 1800 -y 3000 -Y 60 www.far-away-site.com + curl -m 1800 -Y 3000 -y 60 www.far-away-site.com CONFIG FILE -- cgit v1.2.1 From 94bae207765a6c388206799f3b22c2603d738120 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sun, 13 Oct 2002 10:28:38 +0000 Subject: some more --- docs/MANUAL | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 95211ed63..fbdabfb5c 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -411,6 +411,22 @@ SPEED LIMIT curl -m 1800 -Y 3000 -y 60 www.far-away-site.com + Forcing curl not to transfer data faster than a given rate is also possible, + which might be useful if you're using a limited bandwidth connection and you + don't want your transfer to use all of it. + + Make curl transfer data no faster than 10 kilobytes per second: + + curl --limit-rate 10K www.far-away-site.com + + or + + curl --limit-rate 10240 www.far-away-site.com + + Or prevent curl from uploading data faster than 1 megabyte per second: + + curl -T upload --limit-rate 1M ftp://uploadshereplease.com + CONFIG FILE Curl automatically tries to read the .curlrc file (or _curlrc file on win32 @@ -567,8 +583,8 @@ HTTPS Many older SSL-servers have problems with SSLv3 or TLS, that newer versions of OpenSSL etc is using, therefore it is sometimes useful to specify what - SSL-version curl should use. Use -3 or -2 to specify that exact SSL version - to use: + SSL-version curl should use. Use -3, -2 or -1 to specify that exact SSL + version to use (for SSLv3, SSLv2 or TLSv1 respectively): curl -2 https://secure.site.com/ -- cgit v1.2.1 From d442088ed38cf11e56e848523e1fa60c2697e856 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 28 Oct 2002 20:58:28 +0000 Subject: kromJx@crosswinds.net fixed typos --- docs/MANUAL | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index fbdabfb5c..7894bcd54 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -564,7 +564,7 @@ HTTPS from sites that require valid certificates. The only drawback is that the certificate needs to be in PEM-format. PEM is a standard and open format to store certificates with, but it is not used by the most commonly used - browsers (Netscape and MSEI both use the so called PKCS#12 format). If you + browsers (Netscape and MSIE both use the so called PKCS#12 format). If you want curl to use the certificates you use with your (favourite) browser, you may need to download/compile a converter that can convert your browser's formatted certificates to PEM formatted ones. This kind of converter is @@ -842,13 +842,13 @@ MAILING LISTS Receives notifications on all CVS commits done to the curl source module. This can become quite a large amount of mails during intense development, - be aware. This is for us who liks email... + be aware. This is for us who like email... curl-www-commits Receives notifications on all CVS commits done to the curl www module (basicly the web site). This can become quite a large amount of mails - during intense changing, be aware. This is for us who liks email... + during intense changing, be aware. This is for us who like email... Please direct curl questions, feature requests and trouble reports to one of these mailing lists instead of mailing any individual. -- cgit v1.2.1 From 6589579850b09ff6bd3d987dc7172a5eef6f96e5 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 26 Feb 2003 13:01:29 +0000 Subject: random updates --- docs/MANUAL | 37 +++++++++++++++++++++++++++++++------ 1 file changed, 31 insertions(+), 6 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 7894bcd54..87cd8aafe 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -166,13 +166,21 @@ UPLOADING VERBOSE / DEBUG - If curl fails where it isn't supposed to, if the servers don't let you - in, if you can't understand the responses: use the -v flag to get VERBOSE - fetching. Curl will output lots of info and all data it sends and - receives in order to let the user see all client-server interaction. + If curl fails where it isn't supposed to, if the servers don't let you in, + if you can't understand the responses: use the -v flag to get verbose + fetching. Curl will output lots of info and what it sends and receives in + order to let the user see all client-server interaction (but it won't show + you the actual data). curl -v ftp://ftp.upload.com/ + To get even more details and information on what curl does, try using the + --trace or --trace-ascii options with a given file name to log to, like + this: + + curl --trace trace.txt www.haxx.se + + DETAILED INFORMATION Different protocols provide different ways of getting detailed information @@ -350,6 +358,13 @@ COOKIES curl -b headers www.example.com + While saving headers to a file is a working way to store cookies, it is + however error-prone and not the prefered way to do this. Instead, make curl + save the incoming cookies using the well-known netscape cookie format like + this: + + curl -c cookies.txt www.example.com + Note that by specifying -b you enable the "cookie awareness" and with -L you can make curl follow a location: (which often is used in combination with cookies). So that if a site sends cookies and a location, you can @@ -363,7 +378,11 @@ COOKIES the cookies received from www.example.com. curl will send to the server the stored cookies which match the request as it follows the location. The file "empty.txt" may be a non-existant file. - + + Alas, to both read and write cookies from a netscape cookie file, you can + set both -b and -c to use the same file: + + curl -b cookies.txt -c cookies.txt www.example.com PROGRESS METER @@ -413,7 +432,8 @@ SPEED LIMIT Forcing curl not to transfer data faster than a given rate is also possible, which might be useful if you're using a limited bandwidth connection and you - don't want your transfer to use all of it. + don't want your transfer to use all of it (sometimes referred to as + "bandwith throttle"). Make curl transfer data no faster than 10 kilobytes per second: @@ -427,6 +447,11 @@ SPEED LIMIT curl -T upload --limit-rate 1M ftp://uploadshereplease.com + When using the --limit-rate option, the transfer rate is regulated on a + per-second basis, which will cause the total transfer speed to become lower + than the given number. Sometimes of course substantially lower, if your + transfer stalls during periods. + CONFIG FILE Curl automatically tries to read the .curlrc file (or _curlrc file on win32 -- cgit v1.2.1 From 93352e56d809266587eeb4b4c9fe2a8a067d32bd Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 28 Jul 2003 08:53:12 +0000 Subject: As noticed by Kevin Roth, we shall not speak of root dir when it isn't necessarily the root... --- docs/MANUAL | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 87cd8aafe..c0386f7fc 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -11,7 +11,7 @@ SIMPLE USAGE curl http://www.netscape.com/ - Get the root README file from funet's ftp-server: + Get the README file the user's home directory at funet's ftp-server: curl ftp://ftp.funet.fi/README @@ -19,7 +19,7 @@ SIMPLE USAGE curl http://www.weirdserver.com:8000/ - Get a list of the root directory of an FTP site: + Get a list of a directory of an FTP site: curl ftp://cool.haxx.se/ -- cgit v1.2.1 From a358ac24f490bfaa59213fa779f2107ce811b955 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 1 Aug 2003 14:20:48 +0000 Subject: Joerg Mueller-Tolk fixed a minor mistake --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index c0386f7fc..f62ddb39f 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -243,7 +243,7 @@ POST (HTTP) To post to this, you enter a curl command line like: - curl -d "user=foobar&pass=12345&id=blablabla&dig=submit" (continues) + curl -d "user=foobar&pass=12345&id=blablabla&ding=submit" (continues) http://www.formpost.com/getthis/post.cgi -- cgit v1.2.1 From 773a8fe598149531294dae6def5ccfaf996debb5 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 3 Feb 2004 15:59:06 +0000 Subject: no one uses libcurl before 7.7 anyway... --- docs/MANUAL | 2 -- 1 file changed, 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index f62ddb39f..4e3765778 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -836,8 +836,6 @@ PERSISTANT CONNECTIONS transfers faster. If you use a http proxy for file transfers, practicly all transfers will be persistant. - Persistant connections were introduced in curl 7.7. - MAILING LISTS For your convenience, we have several open mailing lists to discuss curl, -- cgit v1.2.1 From ad6699e0c43b8c1495db54652d96cad7e2f800aa Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 26 Mar 2004 13:20:28 +0000 Subject: some more password blurb --- docs/MANUAL | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 4e3765778..f21154144 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -63,6 +63,11 @@ USING PASSWORDS curl -u name:passwd ftp://machine.domain:port/full/path/to/file + FTPS + + It is just like for FTP, but you may also want to specify and use + SSL-specific options for certificates etc. + HTTP The HTTP URL doesn't support user and password in the URL string. Curl @@ -75,6 +80,12 @@ USING PASSWORDS curl -u name:passwd http://machine.domain/full/path/to/file + HTTP offers many different methods of authentication and curl supports + several: Basic, Digest, NTLM and Negotiate. Without telling which method to + use, curl defaults to Basic. You can also ask curl to pick the most secure + ones out of the ones that the server accepts for the given URL, by using + --anyauth. + NOTE! Since HTTP URLs don't support user and password, you can't use that style when using Curl via a proxy. You _must_ use the -u style fetch during such circumstances. -- cgit v1.2.1 From 7dcb1027332e26f59dea184c4755272311195874 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 3 Jun 2004 11:30:30 +0000 Subject: Mention the python-isque mailing list, don't mention the commit mailing lists as they are probably very rarely intresting to the "common people" anyway. --- docs/MANUAL | 20 +++++++------------- 1 file changed, 7 insertions(+), 13 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index f21154144..7ea420d45 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -851,7 +851,7 @@ MAILING LISTS For your convenience, we have several open mailing lists to discuss curl, its development and things relevant to this. Get all info at - http://curl.haxx.se/mail/. The lists available are: + http://curl.haxx.se/mail/. Some of the lists available are: curl-users @@ -865,24 +865,18 @@ MAILING LISTS curl-announce - Low-traffic. Only announcements of new public versions. + Low-traffic. Only receives announcements of new public versions. At worst, + that makes something like one or two mails per month, but usually only one + mail every second month. - curl-and-PHP + curl-and-php Using the curl functions in PHP. Everything curl with a PHP angle. Or PHP with a curl angle. - curl-commits + curl-and-python - Receives notifications on all CVS commits done to the curl source module. - This can become quite a large amount of mails during intense development, - be aware. This is for us who like email... - - curl-www-commits - - Receives notifications on all CVS commits done to the curl www module - (basicly the web site). This can become quite a large amount of mails - during intense changing, be aware. This is for us who like email... + Python hackers using curl with or without the python binding pycurl. Please direct curl questions, feature requests and trouble reports to one of these mailing lists instead of mailing any individual. -- cgit v1.2.1 From 39af394a1c3ae1d8ac71ad263a7c524988702c2e Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 6 Oct 2004 07:50:18 +0000 Subject: removed tabs and trailing whitespace from source --- docs/MANUAL | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 7ea420d45..7eac93a00 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -580,11 +580,11 @@ NETWORK INTERFACE Get a web page from a server using a specified port for the interface: - curl --interface eth0:1 http://www.netscape.com/ + curl --interface eth0:1 http://www.netscape.com/ or - curl --interface 192.168.1.10 http://www.netscape.com/ + curl --interface 192.168.1.10 http://www.netscape.com/ HTTPS -- cgit v1.2.1 From b6f855cb9b6e40907a84799e5c2e8b80f4d3dcb8 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 10 Dec 2004 21:56:35 +0000 Subject: Dan Fandrich corrects spelling mistakes --- docs/MANUAL | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 7eac93a00..26bb8f65a 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -170,8 +170,8 @@ UPLOADING curl -T - http://www.upload.com/myfile - Note that the http server must've been configured to accept PUT before this - can be done successfully. + Note that the http server must have been configured to accept PUT before + this can be done successfully. For other ways to do http data upload, see the POST section below. @@ -370,7 +370,7 @@ COOKIES curl -b headers www.example.com While saving headers to a file is a working way to store cookies, it is - however error-prone and not the prefered way to do this. Instead, make curl + however error-prone and not the preferred way to do this. Instead, make curl save the incoming cookies using the well-known netscape cookie format like this: @@ -388,7 +388,7 @@ COOKIES file contents. In the above command, curl will parse the header and store the cookies received from www.example.com. curl will send to the server the stored cookies which match the request as it follows the location. The - file "empty.txt" may be a non-existant file. + file "empty.txt" may be a nonexistent file. Alas, to both read and write cookies from a netscape cookie file, you can set both -b and -c to use the same file: @@ -417,7 +417,7 @@ PROGRESS METER Upload - the average transfer speed of the upload Time Total - expected time to complete the operation Time Current - time passed since the invoke - Time Left - expected time left to completetion + Time Left - expected time left to completion Curr.Speed - the average transfer speed the last 5 seconds (the first 5 seconds of a transfer is based on less time of course.) @@ -437,14 +437,14 @@ SPEED LIMIT curl -Y 3000 -y 60 www.far-away-site.com This can very well be used in combination with the overall time limit, so - that the above operatioin must be completed in whole within 30 minutes: + that the above operation must be completed in whole within 30 minutes: curl -m 1800 -Y 3000 -y 60 www.far-away-site.com Forcing curl not to transfer data faster than a given rate is also possible, which might be useful if you're using a limited bandwidth connection and you don't want your transfer to use all of it (sometimes referred to as - "bandwith throttle"). + "bandwidth throttle"). Make curl transfer data no faster than 10 kilobytes per second: @@ -590,7 +590,7 @@ HTTPS Secure HTTP requires SSL libraries to be installed and used when curl is built. If that is done, curl is capable of retrieving and posting documents - using the HTTPS procotol. + using the HTTPS protocol. Example: @@ -765,7 +765,7 @@ NETRC to specify name and password for commonly visited ftp sites in a file so that you don't have to type them in each time you visit those sites. You realize this is a big security risk if someone else gets hold of your - passwords, so therefor most unix programs won't read this file unless it is + passwords, so therefore most unix programs won't read this file unless it is only readable by yourself (curl doesn't care though). Curl supports .netrc files if told so (using the -n/--netrc and @@ -830,22 +830,22 @@ TELNET to track when the login prompt is received and send the username and password accordingly. -PERSISTANT CONNECTIONS +PERSISTENT CONNECTIONS Specifying multiple files on a single command line will make curl transfer all of them, one after the other in the specified order. - libcurl will attempt to use persistant connections for the transfers so that + libcurl will attempt to use persistent connections for the transfers so that the second transfer to the same host can use the same connection that was already initiated and was left open in the previous transfer. This greatly decreases connection time for all but the first transfer and it makes a far better use of the network. - Note that curl cannot use persistant connections for transfers that are used + Note that curl cannot use persistent connections for transfers that are used in subsequence curl invokes. Try to stuff as many URLs as possible on the same command line if they are using the same host, as that'll make the - transfers faster. If you use a http proxy for file transfers, practicly - all transfers will be persistant. + transfers faster. If you use a http proxy for file transfers, practically + all transfers will be persistent. MAILING LISTS -- cgit v1.2.1 From 2f8085af15468741266e162af15804061d960d85 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sat, 12 Mar 2005 19:39:27 +0000 Subject: David Houlder added --form-string --- docs/MANUAL | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 26bb8f65a..86449d7d3 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -299,6 +299,13 @@ POST (HTTP) curl -F "docpicture=@dog.gif" -F "catpicture=@cat.gif" + To send a field value literally without interpreting a leading '@' + or '<', or an embedded ';type=', use --form-string instead of + -F. This is recommended when the value is obtained from a user or + some other unpredictable source. Under these circumstances, using + -F instead of --form-string would allow a user to trick curl into + uploading a file. + REFERRER A HTTP request has the option to include information about which address -- cgit v1.2.1 From 67a83c1b3465c44b249eaa44fdc492952e59b31f Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 16 Jan 2006 22:14:37 +0000 Subject: David Shaw finally removed all traces of Gopher and we are now officially not supporting it. It hasn't been functioning for years anyway, so this is just finally stating what already was true. And a cleanup at the same time. --- docs/MANUAL | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 86449d7d3..0622696f5 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -23,10 +23,6 @@ SIMPLE USAGE curl ftp://cool.haxx.se/ - Get a gopher document from funet's gopher server: - - curl gopher://gopher.funet.fi - Get the definition of curl from a dictionary: curl dict://dict.org/m:curl @@ -94,10 +90,6 @@ USING PASSWORDS Probably most commonly used with private certificates, as explained below. - GOPHER - - Curl features no password support for gopher. - PROXY Get an ftp file using a proxy named my-proxy that uses port 888: @@ -748,7 +740,7 @@ ENVIRONMENT VARIABLES Curl reads and understands the following environment variables: - http_proxy, HTTPS_PROXY, FTP_PROXY, GOPHER_PROXY + http_proxy, HTTPS_PROXY, FTP_PROXY They should be set for protocol-specific proxies. General proxy should be set with -- cgit v1.2.1 From fb88723afcb4d19020e18dbe57f13c08e0a9982a Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 25 May 2006 11:15:25 +0000 Subject: minor RFC updates, Dan Fandrich brought my attention to them --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 0622696f5..f849110e1 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -726,7 +726,7 @@ LDAP Working with LDAP URLs": http://developer.netscape.com/docs/manuals/dirsdk/csdk30/url.htm - RFC 2255, "The LDAP URL Format" http://www.rfc-editor.org/rfc/rfc2255.txt + RFC 2255, "The LDAP URL Format" http://curl.haxx.se/rfc/rfc2255.txt To show you an example, this is now I can get all people from my local LDAP server that has a certain sub-domain in their email address: -- cgit v1.2.1 From 52560142bf0a75943323fd5efb2ac6b188066d5f Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 5 Sep 2006 21:17:04 +0000 Subject: added some fresh new blurb --- docs/MANUAL | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index f849110e1..221464ed9 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -31,6 +31,15 @@ SIMPLE USAGE curl ftp://cool.haxx.se/ http://www.weirdserver.com:8000/ + Get a file off an FTPS server: + + curl ftps://files.are.secure.com/secrets.txt + + or use the more appropriate FTPS way to get the same file: + + curl --ftp-ssl ftp://files.are.secure.com/secrets.txt + + DOWNLOAD TO A FILE Get a web page and store in a local file: @@ -64,6 +73,10 @@ USING PASSWORDS It is just like for FTP, but you may also want to specify and use SSL-specific options for certificates etc. + Note that using FTPS:// as prefix is the "implicit" way as described in the + standards while the recommended "explicit" way is done by using FTP:// and + the --ftp-ssl option. + HTTP The HTTP URL doesn't support user and password in the URL string. Curl @@ -105,6 +118,8 @@ PROXY curl -U user:passwd -x my-proxy:888 http://www.get.this/ + curl also supports SOCKS4 and SOCKS5 proxies with --socks4 and --socks5. + See also the environment variables Curl support that offer further proxy control. @@ -846,6 +861,22 @@ PERSISTENT CONNECTIONS transfers faster. If you use a http proxy for file transfers, practically all transfers will be persistent. +MULTIPLE TRANSFERS WITH A SINGLE COMMAND LINE + + As is mentioned above, you can download multiple files with one command line + by simply adding more URLs. If you want those to get saved to a local file + instead of just printed to stdout, you need to add one save option for each + URL you specify. Note that this also goes for the -O option. + + For example: get two files and use -O for the first and a custom file + name for the second: + + curl -O http://url.com/file.txt ftp://ftp.com/moo.exe -o moo.jpg + + You can also upload multiple files in a similar fashion: + + curl -T local1 ftp://ftp.com/moo.exe -T local2 ftp://ftp.com/moo2.txt + MAILING LISTS For your convenience, we have several open mailing lists to discuss curl, -- cgit v1.2.1 From aeddea2b719ad676abcb0f563c888fbba934fdc0 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 1 Mar 2007 21:26:23 +0000 Subject: remove unncessary and wrong remark --- docs/MANUAL | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 221464ed9..5dcd2291f 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -79,9 +79,8 @@ USING PASSWORDS HTTP - The HTTP URL doesn't support user and password in the URL string. Curl - does support that anyway to provide a ftp-style interface and thus you can - pick a file like: + Curl also supports user and password in HTTP URLs, thus you can pick a file + like: curl http://name:passwd@machine.domain/full/path/to/file -- cgit v1.2.1 From f1a8fd843f0aaba9a7feaddc0f1e5a8a888f0fd8 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 22 Mar 2007 15:23:00 +0000 Subject: -z hasn't supported "yesterday" for quite some time... --- docs/MANUAL | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 5dcd2291f..dd063911d 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -699,9 +699,9 @@ TIME CONDITIONS curl -z -local.html http://remote.server.com/remote.html You can specify a "free text" date as condition. Tell curl to only download - the file if it was updated since yesterday: + the file if it was updated since January 12, 2012: - curl -z yesterday http://remote.server.com/remote.html + curl -z "Jan 12 2012" http://remote.server.com/remote.html Curl will then accept a wide range of date formats. You always make the date check the other way around by prepending it with a dash '-'. -- cgit v1.2.1 From 0043e870145d167003931cda2fd90b5e13b0b7f8 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Fri, 23 Mar 2007 17:59:40 +0000 Subject: Added --pubkey option to curl and made --key also work for SCP/SFTP, plus made --pass work on an SSH private key as well. --- docs/MANUAL | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index dd063911d..d087c3b22 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -7,7 +7,7 @@ LATEST VERSION SIMPLE USAGE - Get the main page from netscape's web-server: + Get the main page from Netscape's web-server: curl http://www.netscape.com/ @@ -39,6 +39,15 @@ SIMPLE USAGE curl --ftp-ssl ftp://files.are.secure.com/secrets.txt + Get a file from an SSH server using SFTP: + + curl -u username sftp://shell.example.com/~/personal.txt + + Get a file from an SSH server using SCP using a private key to authenticate: + + curl -u username: --key ~/.ssh/id_dsa --pubkey ~/.ssh/id_dsa.pub \ + scp://shell.example.com/~/personal.txt + DOWNLOAD TO A FILE -- cgit v1.2.1 From 59302d4ba04a63ff39e5fb22b4d79293218bd317 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Thu, 29 Mar 2007 20:44:06 +0000 Subject: Show an absolute sftp: file path to give an additional example. --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index d087c3b22..1ea13f142 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -41,7 +41,7 @@ SIMPLE USAGE Get a file from an SSH server using SFTP: - curl -u username sftp://shell.example.com/~/personal.txt + curl -u username sftp://shell.example.com/etc/issue Get a file from an SSH server using SCP using a private key to authenticate: -- cgit v1.2.1 From 54967d2a3ab5559631407f7b7f67ef48c2dda6dd Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sun, 1 Jul 2007 22:01:18 +0000 Subject: Thomas J. Moore provided a patch that introduces Kerberos5 support in libcurl. This also makes the options change name to --krb (from --krb4) and CURLOPT_KRBLEVEL (from CURLOPT_KRB4LEVEL) but the old names are still --- docs/MANUAL | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 1ea13f142..dba224d91 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -809,18 +809,19 @@ CUSTOM OUTPUT curl -w 'We downloaded %{size_download} bytes\n' www.download.com -KERBEROS4 FTP TRANSFER +KERBEROS FTP TRANSFER - Curl supports kerberos4 for FTP transfers. You need the kerberos package - installed and used at curl build time for it to be used. + Curl supports kerberos4 and kerberos5/GSSAPI for FTP transfers. You need + the kerberos package installed and used at curl build time for it to be + used. - First, get the krb-ticket the normal way, like with the kauth tool. Then use - curl in way similar to: + First, get the krb-ticket the normal way, like with the kinit/kauth tool. + Then use curl in way similar to: - curl --krb4 private ftp://krb4site.com -u username:fakepwd + curl --krb private ftp://krb4site.com -u username:fakepwd There's no use for a password on the -u switch, but a blank one will make - curl ask for one and you already entered the real password to kauth. + curl ask for one and you already entered the real password to kinit/kauth. TELNET -- cgit v1.2.1 From 987b67bd2e827248958a7a6dd6cc3ad0fb484d5c Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Wed, 30 Jul 2008 23:49:20 +0000 Subject: Added IPv6 section --- docs/MANUAL | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index dba224d91..30a932272 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -496,7 +496,7 @@ CONFIG FILE with = or :. Comments can be used within the file. If the first letter on a line is a '#'-letter the rest of the line is treated as a comment. - If you want the parameter to contain spaces, you must inclose the entire + If you want the parameter to contain spaces, you must enclose the entire parameter within double quotes ("). Within those quotes, you specify a quote as \". @@ -567,7 +567,7 @@ FTP and PATH NAMES FTP and firewalls The FTP protocol requires one of the involved parties to open a second - connction as soon as data is about to get transfered. There are two ways to + connection as soon as data is about to get transfered. There are two ways to do this. The default way for curl is to issue the PASV command which causes the @@ -886,6 +886,25 @@ MULTIPLE TRANSFERS WITH A SINGLE COMMAND LINE curl -T local1 ftp://ftp.com/moo.exe -T local2 ftp://ftp.com/moo2.txt +IPv6 + + curl will connect to a server with IPv6 when a host lookup returns an IPv6 + address and fall back to IPv4 if the connection fails. The --ipv4 and --ipv6 + options can specify which address to use when both are available. IPv6 + addresses can also be specified directly in URLs using the syntax: + + http://[2001:1890:1112:1::20]/overview.html + + When this style is used, the -g option must be given to stop curl from + interpreting the square brackets as special globbing characters. Link local + and site local addresses including a scope identifier, such as fe80::1234%1, + may also be used, but the scope portion must be numeric and the percent + character must be URL escaped. The previous example in an SFTP URL might + look like: + + sftp://[fe80::1234%251]/ + + MAILING LISTS For your convenience, we have several open mailing lists to discuss curl, -- cgit v1.2.1 From 660516914e35631714c73a2002ccfa4d854a0290 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Thu, 31 Jul 2008 20:04:00 +0000 Subject: Fixed parsing of an IPv6 proxy address to support a scope identifier, as well as IPv4 addresses in IPv6 format. Also, better handle the case of a malformatted IPv6 address (avoid empty and NULL strings). --- docs/MANUAL | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 30a932272..3b1195c0b 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -904,6 +904,9 @@ IPv6 sftp://[fe80::1234%251]/ + IPv6 addresses provided other than in URLs (e.g. to the --proxy, --interface + or --ftp-port options) should not be URL encoded. + MAILING LISTS -- cgit v1.2.1 From 42cabc14d44b69af1df71f6f1e0ae8ccb66a8287 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Fri, 1 Aug 2008 18:41:14 +0000 Subject: Added support for --append on SFTP uploads. Unfortunately, OpenSSH doesn't support this so it goes untested. --- docs/MANUAL | 29 ++++++++++++++++++++++++----- 1 file changed, 24 insertions(+), 5 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 3b1195c0b..3aea5d40f 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -48,6 +48,9 @@ SIMPLE USAGE curl -u username: --key ~/.ssh/id_dsa --pubkey ~/.ssh/id_dsa.pub \ scp://shell.example.com/~/personal.txt + Get the main page from an IPv6 web server: + + curl -g "http://[2001:1890:1112:1::20]/" DOWNLOAD TO A FILE @@ -86,6 +89,13 @@ USING PASSWORDS standards while the recommended "explicit" way is done by using FTP:// and the --ftp-ssl option. + SFTP / SCP + + This is similar to FTP, but you can specify a private key to use instead of + a password. Note that the private key may itself be protected by a password + that is unrelated to the login password of the remote system. If you + provide a private key file you must also provide a public key file. + HTTP Curl also supports user and password in HTTP URLs, thus you can pick a file @@ -154,9 +164,9 @@ RANGES UPLOADING - FTP + FTP / FTPS / SFTP / SCP - Upload all data on stdin to a specified ftp site: + Upload all data on stdin to a specified server: curl -T - ftp://ftp.upload.com/myfile @@ -169,7 +179,7 @@ UPLOADING curl -T uploadfile -u user:passwd ftp://ftp.upload.com/ - Upload a local file to get appended to the remote file using ftp: + Upload a local file to get appended to the remote file: curl -T localfile -a ftp://ftp.upload.com/remotefile @@ -331,7 +341,7 @@ REFERRER curl -e www.coolsite.com http://www.showme.com/ - NOTE: The referer field is defined in the HTTP spec to be a full URL. + NOTE: The Referer: [sic] field is defined in the HTTP spec to be a full URL. USER AGENT @@ -564,6 +574,14 @@ FTP and PATH NAMES (I.e with an extra slash in front of the file name.) +SFTP and SCP and PATH NAMES + + With sftp: and scp: URLs, the path name given is the absolute name on the + server. To access a file relative to the remote user's home directory, + prefix the file with /~/ , such as: + + curl -u $USER sftp://home.example.com/~/.bashrc + FTP and firewalls The FTP protocol requires one of the involved parties to open a second @@ -875,7 +893,8 @@ MULTIPLE TRANSFERS WITH A SINGLE COMMAND LINE As is mentioned above, you can download multiple files with one command line by simply adding more URLs. If you want those to get saved to a local file instead of just printed to stdout, you need to add one save option for each - URL you specify. Note that this also goes for the -O option. + URL you specify. Note that this also goes for the -O option (but not + --remote-name-all). For example: get two files and use -O for the first and a custom file name for the second: -- cgit v1.2.1 From 5aeef9c1c87f2f72f10807a609ced1976ab46cd2 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sun, 25 Jan 2009 23:26:25 +0000 Subject: - Craig A West brought CURLOPT_NOPROXY and the corresponding --noproxy option. They basically offer the same thing the NO_PROXY environment variable only offered previously: list a set of host names that shall not use the proxy even if one is specified. --- docs/MANUAL | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 3aea5d40f..de2bdd280 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -136,6 +136,11 @@ PROXY curl -U user:passwd -x my-proxy:888 http://www.get.this/ + A comma-separated list of hosts and domains which do not use the proxy can + be specified as: + + curl --noproxy localhost,get.this -x my-proxy:888 http://www.get.this/ + curl also supports SOCKS4 and SOCKS5 proxies with --socks4 and --socks5. See also the environment variables Curl support that offer further proxy @@ -793,8 +798,9 @@ ENVIRONMENT VARIABLES NO_PROXY - If a tail substring of the domain-path for a host matches one of these - strings, transactions with that node will not be proxied. + If the host name matches one of these strings, or the host is within the + domain of one of these strings, transactions with that node will not be + proxied. The usage of the -x/--proxy flag overrides the environment variables. -- cgit v1.2.1 From bdd4294e79eea15cb6f312f7ee7d388ad40a65e3 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 2 Feb 2009 16:19:23 +0000 Subject: - Craig A West brought us: libcurl now defaults to do CONNECT with HTTP version 1.1 instead of 1.0 like before. This change also introduces the new proxy type for libcurl called 'CURLPROXY_HTTP_1_0' that then allows apps to switch (back) to CONNECT 1.0 requests. The curl tool also got a --proxy1.0 option that works exactly like --proxy but sets CURLPROXY_HTTP_1_0. I updated all test cases cases that use CONNECT and I tried to do some using --proxy1.0 and some updated to do CONNECT 1.1 to get both versions run. --- docs/MANUAL | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index de2bdd280..417befb37 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -141,6 +141,9 @@ PROXY curl --noproxy localhost,get.this -x my-proxy:888 http://www.get.this/ + If the proxy is specified with --proxy1.0 instead of --proxy or -x, then + curl will use HTTP/1.0 instead of HTTP/1.1 for any CONNECT attempts. + curl also supports SOCKS4 and SOCKS5 proxies with --socks4 and --socks5. See also the environment variables Curl support that offer further proxy -- cgit v1.2.1 From 07d46886dfa8e2712728930a2912cd24ee4b6a7e Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 13 Feb 2009 09:12:52 +0000 Subject: Anthony Bryan's letter=>symbol fixes --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 417befb37..b59231a03 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -512,7 +512,7 @@ CONFIG FILE can also specify the long options without the dashes to make it more readable. You can separate the options and the parameter with spaces, or with = or :. Comments can be used within the file. If the first letter on a - line is a '#'-letter the rest of the line is treated as a comment. + line is a '#'-symbol the rest of the line is treated as a comment. If you want the parameter to contain spaces, you must enclose the entire parameter within double quotes ("). Within those quotes, you specify a -- cgit v1.2.1 From a07bc79117971b96ebf3188c0a34a73ee0a3609b Mon Sep 17 00:00:00 2001 From: Yang Tse Date: Sun, 14 Feb 2010 19:40:18 +0000 Subject: removed trailing whitespace --- docs/MANUAL | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index b59231a03..208fc79c7 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -168,7 +168,7 @@ RANGES Get the first 100 bytes of a document using FTP: - curl -r 0-99 ftp://www.get.this/README + curl -r 0-99 ftp://www.get.this/README UPLOADING @@ -184,7 +184,7 @@ UPLOADING Upload a local file to the remote site, and use the local file name remote too: - + curl -T uploadfile -u user:passwd ftp://ftp.upload.com/ Upload a local file to get appended to the remote file: @@ -223,7 +223,7 @@ VERBOSE / DEBUG this: curl --trace trace.txt www.haxx.se - + DETAILED INFORMATION @@ -325,12 +325,12 @@ POST (HTTP) To send two files in one post you can do it in two ways: 1. Send multiple files in a single "field" with a single field name: - - curl -F "pictures=@dog.gif,cat.gif" - - 2. Send two fields with two field names: - curl -F "docpicture=@dog.gif" -F "catpicture=@cat.gif" + curl -F "pictures=@dog.gif,cat.gif" + + 2. Send two fields with two field names: + + curl -F "docpicture=@dog.gif" -F "catpicture=@cat.gif" To send a field value literally without interpreting a leading '@' or '<', or an embedded ';type=', use --form-string instead of @@ -678,15 +678,15 @@ HTTPS formatted one that curl can use, do something like this (assuming netscape, but IE is likely to work similarly): - You start with hitting the 'security' menu button in netscape. + You start with hitting the 'security' menu button in netscape. - Select 'certificates->yours' and then pick a certificate in the list + Select 'certificates->yours' and then pick a certificate in the list - Press the 'export' button + Press the 'export' button - enter your PIN code for the certs + enter your PIN code for the certs - select a proper place to save it + select a proper place to save it Run the 'openssl' application to convert the certificate. If you cd to the openssl installation, you can do it like: @@ -793,7 +793,7 @@ ENVIRONMENT VARIABLES They should be set for protocol-specific proxies. General proxy should be set with - + ALL_PROXY A comma-separated list of host names that shouldn't go through any proxy is -- cgit v1.2.1 From 46b112bcd439f4413925a7300d66a3e6f148765e Mon Sep 17 00:00:00 2001 From: Yang Tse Date: Tue, 16 Feb 2010 13:32:45 +0000 Subject: replaced tabs with spaces --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 208fc79c7..d7085b7f6 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -46,7 +46,7 @@ SIMPLE USAGE Get a file from an SSH server using SCP using a private key to authenticate: curl -u username: --key ~/.ssh/id_dsa --pubkey ~/.ssh/id_dsa.pub \ - scp://shell.example.com/~/personal.txt + scp://shell.example.com/~/personal.txt Get the main page from an IPv6 web server: -- cgit v1.2.1 From 2f6924032a8e0d28b53036aa49661d627af0e2bd Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Thu, 7 Apr 2011 11:31:39 -0700 Subject: Added mention of FTP proxies --- docs/MANUAL | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index d7085b7f6..ce617138f 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -123,7 +123,13 @@ USING PASSWORDS PROXY - Get an ftp file using a proxy named my-proxy that uses port 888: + curl supports both HTTP and SOCKS proxy servers, with optional authentication. + It does not have special support for FTP proxy servers since there are no + standards for those, but it can still be made to work with many of them. You + can also use both HTTP and SOCKS proxies to transfer files to and from FTP + servers. + + Get an ftp file using an HTTP proxy named my-proxy that uses port 888: curl -x my-proxy:888 ftp://ftp.leachsite.com/README @@ -146,9 +152,23 @@ PROXY curl also supports SOCKS4 and SOCKS5 proxies with --socks4 and --socks5. - See also the environment variables Curl support that offer further proxy + See also the environment variables Curl supports that offer further proxy control. + Most FTP proxy servers are set up to appear as a normal FTP server from the + client's perspective, with special commands to select the remote FTP server. + curl supports the -u, -Q and --ftp-account options that can be used to + set up transfers through many FTP proxies. For example, a file can be + uploaded to a remote FTP server using a Blue Coat FTP proxy with the + options: + + curl -u "Remote-FTP-Username@remote.ftp.server Proxy-Username:Remote-Pass" \ + --ftp-account Proxy-Password --upload-file local-file \ + ftp://my-ftp.proxy.server:21/remote/upload/path/ + + See the manual for your FTP proxy to determine the form it expects to set up + transfers, and curl's -v option to see exactly what curl is sending. + RANGES With HTTP 1.1 byte-ranges were introduced. Using this, a client can request -- cgit v1.2.1 From 612a61b267a95d3ac1dddc2f579888c7a595ddbd Mon Sep 17 00:00:00 2001 From: Colin Hogben Date: Wed, 14 Dec 2011 13:30:54 +0000 Subject: Correct default upload mimetype in manual The default content-type for file uploads is application/octet-stream, not text/plain as stated in the MANUAL. --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index ce617138f..da073104c 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -328,7 +328,7 @@ POST (HTTP) If the content-type is not specified, curl will try to guess from the file extension (it only knows a few), or use the previously specified type (from an earlier file if several files are specified in a list) or else it will - using the default type 'text/plain'. + use the default type 'application/octet-stream'. Emulate a fill-in form with -F. Let's say you fill in three fields in a form. One field is a file name which to post, one field is your name and one -- cgit v1.2.1 From cb787b70bf5fa16bc1f83405c16d6c092e6daf46 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Fri, 20 Jul 2012 21:02:58 +0200 Subject: Fixed some typos in documentation --- docs/MANUAL | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index da073104c..b78d57d81 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -613,7 +613,7 @@ SFTP and SCP and PATH NAMES FTP and firewalls The FTP protocol requires one of the involved parties to open a second - connection as soon as data is about to get transfered. There are two ways to + connection as soon as data is about to get transferred. There are two ways to do this. The default way for curl is to issue the PASV command which causes the -- cgit v1.2.1 From d22186bbbcbe224f9333fe94743f8cf141719c78 Mon Sep 17 00:00:00 2001 From: Ant Bryan Date: Mon, 13 Aug 2012 16:32:42 -0400 Subject: MANUAL review --- docs/MANUAL | 103 +++++++++++++++++++++++++++++++++++++++--------------------- 1 file changed, 67 insertions(+), 36 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index b78d57d81..6dbfd24b5 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -19,7 +19,7 @@ SIMPLE USAGE curl http://www.weirdserver.com:8000/ - Get a list of a directory of an FTP site: + Get a directory listing of an FTP site: curl ftp://cool.haxx.se/ @@ -54,7 +54,7 @@ SIMPLE USAGE DOWNLOAD TO A FILE - Get a web page and store in a local file: + Get a web page and store in a local file with a specific name: curl -o thatpage.html http://www.netscape.com/ @@ -133,7 +133,7 @@ PROXY curl -x my-proxy:888 ftp://ftp.leachsite.com/README - Get a file from a HTTP server that requires user and password, using the + Get a file from an HTTP server that requires user and password, using the same proxy as above: curl -u user:passwd -x my-proxy:888 http://www.get.this/ @@ -171,7 +171,7 @@ PROXY RANGES - With HTTP 1.1 byte-ranges were introduced. Using this, a client can request + HTTP 1.1 introduced byte-ranges. Using this, a client can request to get only one or more subparts of a specified document. Curl supports this with the -r flag. @@ -202,8 +202,8 @@ UPLOADING curl -T uploadfile -u user:passwd ftp://ftp.upload.com/myfile - Upload a local file to the remote site, and use the local file name remote - too: + Upload a local file to the remote site, and use the local file name at the remote + site too: curl -T uploadfile -u user:passwd ftp://ftp.upload.com/ @@ -219,14 +219,14 @@ UPLOADING HTTP - Upload all data on stdin to a specified http site: + Upload all data on stdin to a specified HTTP site: curl -T - http://www.upload.com/myfile - Note that the http server must have been configured to accept PUT before + Note that the HTTP server must have been configured to accept PUT before this can be done successfully. - For other ways to do http data upload, see the POST section below. + For other ways to do HTTP data upload, see the POST section below. VERBOSE / DEBUG @@ -289,7 +289,7 @@ POST (HTTP) The 'variable' names are the names set with "name=" in the tags, and the data is the contents you want to fill in for the inputs. The data *must* be properly URL encoded. That means you replace space with + and that you - write weird letters with %XX where XX is the hexadecimal representation of + replace weird letters with %XX where XX is the hexadecimal representation of the letter's ASCII code. Example: @@ -361,8 +361,8 @@ POST (HTTP) REFERRER - A HTTP request has the option to include information about which address - that referred to actual page. Curl allows you to specify the + An HTTP request has the option to include information about which address + referred it to the actual page. Curl allows you to specify the referrer to be used on the command line. It is especially useful to fool or trick stupid servers or CGI scripts that rely on that information being available or contain certain data. @@ -373,7 +373,7 @@ REFERRER USER AGENT - A HTTP request has the option to include information about the browser + An HTTP request has the option to include information about the browser that generated the request. Curl allows it to be specified on the command line. It is especially useful to fool or trick stupid servers or CGI scripts that only accept certain browsers. @@ -618,16 +618,16 @@ FTP and firewalls The default way for curl is to issue the PASV command which causes the server to open another port and await another connection performed by the - client. This is good if the client is behind a firewall that don't allow + client. This is good if the client is behind a firewall that doesn't allow incoming connections. curl ftp.download.com - If the server for example, is behind a firewall that don't allow connections - on other ports than 21 (or if it just doesn't support the PASV command), the + If the server, for example, is behind a firewall that doesn't allow connections + on ports other than 21 (or if it just doesn't support the PASV command), the other way to do it is to use the PORT command and instruct the server to - connect to the client on the given (as parameters to the PORT command) IP - number and port. + connect to the client on the given IP number and port (as parameters to the + PORT command). The -P flag to curl supports a few different options. Your machine may have several IP-addresses and/or network interfaces and curl allows you to select @@ -685,8 +685,8 @@ HTTPS If you neglect to specify the password on the command line, you will be prompted for the correct password before any data can be received. - Many older SSL-servers have problems with SSLv3 or TLS, that newer versions - of OpenSSL etc is using, therefore it is sometimes useful to specify what + Many older SSL-servers have problems with SSLv3 or TLS, which newer versions + of OpenSSL etc use, therefore it is sometimes useful to specify what SSL-version curl should use. Use -3, -2 or -1 to specify that exact SSL version to use (for SSLv3, SSLv2 or TLSv1 respectively): @@ -695,14 +695,13 @@ HTTPS Otherwise, curl will first attempt to use v3 and then v2. To use OpenSSL to convert your favourite browser's certificate into a PEM - formatted one that curl can use, do something like this (assuming netscape, - but IE is likely to work similarly): + formatted one that curl can use, do something like this: - You start with hitting the 'security' menu button in netscape. + In Netscape, you start with hitting the 'Security' menu button. Select 'certificates->yours' and then pick a certificate in the list - Press the 'export' button + Press the 'Export' button enter your PIN code for the certs @@ -713,11 +712,21 @@ HTTPS # ./apps/openssl pkcs12 -in [file you saved] -clcerts -out [PEMfile] + In Firefox, select Options, then Advanced, then the Encryption tab, + View Certificates. This opens the Certificate Manager, where you can + Export. Be sure to select PEM for the Save as type. + + In Internet Explorer, select Internet Options, then the Content tab, then + Certificates. Then you can Export, and depending on the format you may + need to convert to PEM. + + In Chrome, select Settings, then Show Advanced Settings. Under HTTPS/SSL + select Manage Certificates. RESUMING FILE TRANSFERS To continue a file transfer where it was previously aborted, curl supports - resume on http(s) downloads as well as ftp uploads and downloads. + resume on HTTP(S) downloads as well as FTP uploads and downloads. Continue downloading a document: @@ -731,7 +740,7 @@ RESUMING FILE TRANSFERS curl -C - -o file http://www.server.com/ - (*1) = This requires that the ftp server supports the non-standard command + (*1) = This requires that the FTP server supports the non-standard command SIZE. If it doesn't, curl will say so. (*2) = This requires that the web server supports at least HTTP/1.1. If it @@ -740,7 +749,7 @@ RESUMING FILE TRANSFERS TIME CONDITIONS HTTP allows a client to specify a time condition for the document it - requests. It is If-Modified-Since or If-Unmodified-Since. Curl allow you to + requests. It is If-Modified-Since or If-Unmodified-Since. Curl allows you to specify them with the -z/--time-cond flag. For example, you can easily make a download that only gets performed if the @@ -788,7 +797,7 @@ LDAP and offer ldap:// support. LDAP is a complex thing and writing an LDAP query is not an easy task. I do - advice you to dig up the syntax description for that elsewhere. Two places + advise you to dig up the syntax description for that elsewhere. Two places that might suit you are: Netscape's "Netscape Directory SDK 3.0 for C Programmer's Guide Chapter 10: @@ -797,7 +806,7 @@ LDAP RFC 2255, "The LDAP URL Format" http://curl.haxx.se/rfc/rfc2255.txt - To show you an example, this is now I can get all people from my local LDAP + To show you an example, this is how I can get all people from my local LDAP server that has a certain sub-domain in their email address: curl -B "ldap://ldap.frontec.se/o=frontec??sub?mail=*sth.frontec.se" @@ -831,15 +840,15 @@ ENVIRONMENT VARIABLES NETRC Unix introduced the .netrc concept a long time ago. It is a way for a user - to specify name and password for commonly visited ftp sites in a file so + to specify name and password for commonly visited FTP sites in a file so that you don't have to type them in each time you visit those sites. You realize this is a big security risk if someone else gets hold of your passwords, so therefore most unix programs won't read this file unless it is only readable by yourself (curl doesn't care though). - Curl supports .netrc files if told so (using the -n/--netrc and - --netrc-optional options). This is not restricted to only ftp, - but curl can use it for all protocols where authentication is used. + Curl supports .netrc files if told to (using the -n/--netrc and + --netrc-optional options). This is not restricted to just FTP, + so curl can use it for all protocols where authentication is used. A very simple .netrc file could look something like: @@ -860,7 +869,7 @@ KERBEROS FTP TRANSFER Curl supports kerberos4 and kerberos5/GSSAPI for FTP transfers. You need the kerberos package installed and used at curl build time for it to be - used. + available. First, get the krb-ticket the normal way, like with the kinit/kauth tool. Then use curl in way similar to: @@ -895,7 +904,7 @@ TELNET - NEW_ENV= Sets an environment variable. - NOTE: the telnet protocol does not specify any way to login with a specified + NOTE: The telnet protocol does not specify any way to login with a specified user and password so curl can't do that automatically. To do that, you need to track when the login prompt is received and send the username and password accordingly. @@ -914,7 +923,7 @@ PERSISTENT CONNECTIONS Note that curl cannot use persistent connections for transfers that are used in subsequence curl invokes. Try to stuff as many URLs as possible on the same command line if they are using the same host, as that'll make the - transfers faster. If you use a http proxy for file transfers, practically + transfers faster. If you use an HTTP proxy for file transfers, practically all transfers will be persistent. MULTIPLE TRANSFERS WITH A SINGLE COMMAND LINE @@ -955,6 +964,28 @@ IPv6 IPv6 addresses provided other than in URLs (e.g. to the --proxy, --interface or --ftp-port options) should not be URL encoded. +METALINK + + Curl supports Metalink (both version 3 and 4 (RFC 5854) are supported), a way + to list multiple URIs and hashes for a file. Curl will make use of the mirrors + listed within for failover if there are errors (such as the file or server not + being available). It will also verify the hash of the file after the download + completes. The Metalink file itself is downloaded and processed in memory and + not stored in the local file system. + + Example to use a remote Metalink file: + + curl --metalink http://www.example.com/example.metalink + + To use a Metalink file in the local file system, use FILE protocol (file://): + + curl --metalink file://example.metalink + + Please note that if FILE protocol is disabled, there is no way to use a local + Metalink file at the time of this writing. Also note that if --metalink and + --include are used together, --include will be ignored. This is because including + headers in the response will break Metalink parser and if the headers are included + in the file described in Metalink file, hash check will fail. MAILING LISTS -- cgit v1.2.1 From fa4b4d2033bd79bcc40e754b19ca50849e2e0e69 Mon Sep 17 00:00:00 2001 From: Anthony Bryan Date: Sun, 9 Sep 2012 23:08:59 +0200 Subject: MANUAL: clarified user+password in HTTP URLs --- docs/MANUAL | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs/MANUAL') diff --git a/docs/MANUAL b/docs/MANUAL index 6dbfd24b5..4ad2e135e 100644 --- a/docs/MANUAL +++ b/docs/MANUAL @@ -113,9 +113,10 @@ USING PASSWORDS ones out of the ones that the server accepts for the given URL, by using --anyauth. - NOTE! Since HTTP URLs don't support user and password, you can't use that - style when using Curl via a proxy. You _must_ use the -u style fetch - during such circumstances. + NOTE! According to the URL specification, HTTP URLs can not contain a user + and password, so that style will not work when using curl via a proxy, even + though curl allows it at other times. When using a proxy, you _must_ use + the -u style for user and password. HTTPS -- cgit v1.2.1