3 You always find news about what's going on as well as the latest versions
4 from the curl web pages, located at:
10 Get the main page from netscape's web-server:
12 curl http://www.netscape.com/
14 Get the README file the user's home directory at funet's ftp-server:
16 curl ftp://ftp.funet.fi/README
18 Get a web page from a server using port 8000:
20 curl http://www.weirdserver.com:8000/
22 Get a list of a directory of an FTP site:
24 curl ftp://cool.haxx.se/
26 Get a gopher document from funet's gopher server:
28 curl gopher://gopher.funet.fi
30 Get the definition of curl from a dictionary:
32 curl dict://dict.org/m:curl
34 Fetch two documents at once:
36 curl ftp://cool.haxx.se/ http://www.weirdserver.com:8000/
40 Get a web page and store in a local file:
42 curl -o thatpage.html http://www.netscape.com/
44 Get a web page and store in a local file, make the local file get the name
45 of the remote document (if no file name part is specified in the URL, this
48 curl -O http://www.netscape.com/index.html
50 Fetch two files and store them with their remote names:
52 curl -O www.haxx.se/index.html -O curl.haxx.se/download.html
58 To ftp files using name+passwd, include them in the URL like:
60 curl ftp://name:passwd@machine.domain:port/full/path/to/file
62 or specify them with the -u flag like
64 curl -u name:passwd ftp://machine.domain:port/full/path/to/file
68 The HTTP URL doesn't support user and password in the URL string. Curl
69 does support that anyway to provide a ftp-style interface and thus you can
72 curl http://name:passwd@machine.domain/full/path/to/file
74 or specify user and password separately like in
76 curl -u name:passwd http://machine.domain/full/path/to/file
78 NOTE! Since HTTP URLs don't support user and password, you can't use that
79 style when using Curl via a proxy. You _must_ use the -u style fetch
80 during such circumstances.
84 Probably most commonly used with private certificates, as explained below.
88 Curl features no password support for gopher.
92 Get an ftp file using a proxy named my-proxy that uses port 888:
94 curl -x my-proxy:888 ftp://ftp.leachsite.com/README
96 Get a file from a HTTP server that requires user and password, using the
99 curl -u user:passwd -x my-proxy:888 http://www.get.this/
101 Some proxies require special authentication. Specify by using -U as above:
103 curl -U user:passwd -x my-proxy:888 http://www.get.this/
105 See also the environment variables Curl support that offer further proxy
110 With HTTP 1.1 byte-ranges were introduced. Using this, a client can request
111 to get only one or more subparts of a specified document. Curl supports
112 this with the -r flag.
114 Get the first 100 bytes of a document:
116 curl -r 0-99 http://www.get.this/
118 Get the last 500 bytes of a document:
120 curl -r -500 http://www.get.this/
122 Curl also supports simple ranges for FTP files as well. Then you can only
123 specify start and stop position.
125 Get the first 100 bytes of a document using FTP:
127 curl -r 0-99 ftp://www.get.this/README
133 Upload all data on stdin to a specified ftp site:
135 curl -T - ftp://ftp.upload.com/myfile
137 Upload data from a specified file, login with user and password:
139 curl -T uploadfile -u user:passwd ftp://ftp.upload.com/myfile
141 Upload a local file to the remote site, and use the local file name remote
144 curl -T uploadfile -u user:passwd ftp://ftp.upload.com/
146 Upload a local file to get appended to the remote file using ftp:
148 curl -T localfile -a ftp://ftp.upload.com/remotefile
150 Curl also supports ftp upload through a proxy, but only if the proxy is
151 configured to allow that kind of tunneling. If it does, you can run curl in
152 a fashion similar to:
154 curl --proxytunnel -x proxy:port -T localfile ftp.upload.com
158 Upload all data on stdin to a specified http site:
160 curl -T - http://www.upload.com/myfile
162 Note that the http server must've been configured to accept PUT before this
163 can be done successfully.
165 For other ways to do http data upload, see the POST section below.
169 If curl fails where it isn't supposed to, if the servers don't let you in,
170 if you can't understand the responses: use the -v flag to get verbose
171 fetching. Curl will output lots of info and what it sends and receives in
172 order to let the user see all client-server interaction (but it won't show
173 you the actual data).
175 curl -v ftp://ftp.upload.com/
177 To get even more details and information on what curl does, try using the
178 --trace or --trace-ascii options with a given file name to log to, like
181 curl --trace trace.txt www.haxx.se
186 Different protocols provide different ways of getting detailed information
187 about specific files/documents. To get curl to show detailed information
188 about a single file, you should use -I/--head option. It displays all
189 available info on a single file for HTTP and FTP. The HTTP information is a
192 For HTTP, you can get the header information (the same as -I would show)
193 shown before the data by using -i/--include. Curl understands the
194 -D/--dump-header option when getting files from both FTP and HTTP, and it
195 will then store the headers in the specified file.
197 Store the HTTP headers in a separate file (headers.txt in the example):
199 curl --dump-header headers.txt curl.haxx.se
201 Note that headers stored in a separate file can be very useful at a later
202 time if you want curl to use cookies sent by the server. More about that in
207 It's easy to post data using curl. This is done using the -d <data>
208 option. The post data must be urlencoded.
210 Post a simple "name" and "phone" guestbook.
212 curl -d "name=Rafael%20Sagula&phone=3320780" \
213 http://www.where.com/guest.cgi
215 How to post a form with curl, lesson #1:
217 Dig out all the <input> tags in the form that you want to fill in. (There's
218 a perl program called formfind.pl on the curl site that helps with this).
220 If there's a "normal" post, you use -d to post. -d takes a full "post
221 string", which is in the format
223 <variable1>=<data1>&<variable2>=<data2>&...
225 The 'variable' names are the names set with "name=" in the <input> tags, and
226 the data is the contents you want to fill in for the inputs. The data *must*
227 be properly URL encoded. That means you replace space with + and that you
228 write weird letters with %XX where XX is the hexadecimal representation of
229 the letter's ASCII code.
233 (page located at http://www.formpost.com/getthis/
235 <form action="post.cgi" method="post">
236 <input name=user size=10>
237 <input name=pass type=password size=10>
238 <input name=id type=hidden value="blablabla">
239 <input name=ding value="submit">
242 We want to enter user 'foobar' with password '12345'.
244 To post to this, you enter a curl command line like:
246 curl -d "user=foobar&pass=12345&id=blablabla&ding=submit" (continues)
247 http://www.formpost.com/getthis/post.cgi
250 While -d uses the application/x-www-form-urlencoded mime-type, generally
251 understood by CGI's and similar, curl also supports the more capable
252 multipart/form-data type. This latter type supports things like file upload.
254 -F accepts parameters like -F "name=contents". If you want the contents to
255 be read from a file, use <@filename> as contents. When specifying a file,
256 you can also specify the file content type by appending ';type=<mime type>'
257 to the file name. You can also post the contents of several files in one
258 field. For example, the field name 'coolfiles' is used to send three files,
259 with different content types using the following syntax:
261 curl -F "coolfiles=@fil1.gif;type=image/gif,fil2.txt,fil3.html" \
262 http://www.post.com/postit.cgi
264 If the content-type is not specified, curl will try to guess from the file
265 extension (it only knows a few), or use the previously specified type (from
266 an earlier file if several files are specified in a list) or else it will
267 using the default type 'text/plain'.
269 Emulate a fill-in form with -F. Let's say you fill in three fields in a
270 form. One field is a file name which to post, one field is your name and one
271 field is a file description. We want to post the file we have written named
272 "cooltext.txt". To let curl do the posting of this data instead of your
273 favourite browser, you have to read the HTML source of the form page and
274 find the names of the input fields. In our example, the input field names
275 are 'file', 'yourname' and 'filedescription'.
277 curl -F "file=@cooltext.txt" -F "yourname=Daniel" \
278 -F "filedescription=Cool text file with cool text inside" \
279 http://www.post.com/postit.cgi
281 To send two files in one post you can do it in two ways:
283 1. Send multiple files in a single "field" with a single field name:
285 curl -F "pictures=@dog.gif,cat.gif"
287 2. Send two fields with two field names:
289 curl -F "docpicture=@dog.gif" -F "catpicture=@cat.gif"
293 A HTTP request has the option to include information about which address
294 that referred to actual page. Curl allows you to specify the
295 referrer to be used on the command line. It is especially useful to
296 fool or trick stupid servers or CGI scripts that rely on that information
297 being available or contain certain data.
299 curl -e www.coolsite.com http://www.showme.com/
301 NOTE: The referer field is defined in the HTTP spec to be a full URL.
305 A HTTP request has the option to include information about the browser
306 that generated the request. Curl allows it to be specified on the command
307 line. It is especially useful to fool or trick stupid servers or CGI
308 scripts that only accept certain browsers.
312 curl -A 'Mozilla/3.0 (Win95; I)' http://www.nationsbank.com/
314 Other common strings:
315 'Mozilla/3.0 (Win95; I)' Netscape Version 3 for Windows 95
316 'Mozilla/3.04 (Win95; U)' Netscape Version 3 for Windows 95
317 'Mozilla/2.02 (OS/2; U)' Netscape Version 2 for OS/2
318 'Mozilla/4.04 [en] (X11; U; AIX 4.2; Nav)' NS for AIX
319 'Mozilla/4.05 [en] (X11; U; Linux 2.0.32 i586)' NS for Linux
321 Note that Internet Explorer tries hard to be compatible in every way:
322 'Mozilla/4.0 (compatible; MSIE 4.01; Windows 95)' MSIE for W95
324 Mozilla is not the only possible User-Agent name:
325 'Konqueror/1.0' KDE File Manager desktop client
326 'Lynx/2.7.1 libwww-FM/2.14' Lynx command line browser
330 Cookies are generally used by web servers to keep state information at the
331 client's side. The server sets cookies by sending a response line in the
332 headers that looks like 'Set-Cookie: <data>' where the data part then
333 typically contains a set of NAME=VALUE pairs (separated by semicolons ';'
334 like "NAME1=VALUE1; NAME2=VALUE2;"). The server can also specify for what
335 path the "cookie" should be used for (by specifying "path=value"), when the
336 cookie should expire ("expire=DATE"), for what domain to use it
337 ("domain=NAME") and if it should be used on secure connections only
340 If you've received a page from a server that contains a header like:
341 Set-Cookie: sessionid=boo123; path="/foo";
343 it means the server wants that first pair passed on when we get anything in
344 a path beginning with "/foo".
346 Example, get a page that wants my name passed in a cookie:
348 curl -b "name=Daniel" www.sillypage.com
350 Curl also has the ability to use previously received cookies in following
351 sessions. If you get cookies from a server and store them in a file in a
354 curl --dump-header headers www.example.com
356 ... you can then in a second connect to that (or another) site, use the
357 cookies from the 'headers' file like:
359 curl -b headers www.example.com
361 While saving headers to a file is a working way to store cookies, it is
362 however error-prone and not the prefered way to do this. Instead, make curl
363 save the incoming cookies using the well-known netscape cookie format like
366 curl -c cookies.txt www.example.com
368 Note that by specifying -b you enable the "cookie awareness" and with -L
369 you can make curl follow a location: (which often is used in combination
370 with cookies). So that if a site sends cookies and a location, you can
371 use a non-existing file to trigger the cookie awareness like:
373 curl -L -b empty.txt www.example.com
375 The file to read cookies from must be formatted using plain HTTP headers OR
376 as netscape's cookie file. Curl will determine what kind it is based on the
377 file contents. In the above command, curl will parse the header and store
378 the cookies received from www.example.com. curl will send to the server the
379 stored cookies which match the request as it follows the location. The
380 file "empty.txt" may be a non-existant file.
382 Alas, to both read and write cookies from a netscape cookie file, you can
383 set both -b and -c to use the same file:
385 curl -b cookies.txt -c cookies.txt www.example.com
389 The progress meter exists to show a user that something actually is
390 happening. The different fields in the output have the following meaning:
392 % Total % Received % Xferd Average Speed Time Curr.
393 Dload Upload Total Current Left Speed
394 0 151M 0 38608 0 0 9406 0 4:41:43 0:00:04 4:41:39 9287
397 % - percentage completed of the whole transfer
398 Total - total size of the whole expected transfer
399 % - percentage completed of the download
400 Received - currently downloaded amount of bytes
401 % - percentage completed of the upload
402 Xferd - currently uploaded amount of bytes
404 Dload - the average transfer speed of the download
406 Upload - the average transfer speed of the upload
407 Time Total - expected time to complete the operation
408 Time Current - time passed since the invoke
409 Time Left - expected time left to completetion
410 Curr.Speed - the average transfer speed the last 5 seconds (the first
411 5 seconds of a transfer is based on less time of course.)
413 The -# option will display a totally different progress bar that doesn't
414 need much explanation!
418 Curl allows the user to set the transfer speed conditions that must be met
419 to let the transfer keep going. By using the switch -y and -Y you
420 can make curl abort transfers if the transfer speed is below the specified
421 lowest limit for a specified time.
423 To have curl abort the download if the speed is slower than 3000 bytes per
424 second for 1 minute, run:
426 curl -Y 3000 -y 60 www.far-away-site.com
428 This can very well be used in combination with the overall time limit, so
429 that the above operatioin must be completed in whole within 30 minutes:
431 curl -m 1800 -Y 3000 -y 60 www.far-away-site.com
433 Forcing curl not to transfer data faster than a given rate is also possible,
434 which might be useful if you're using a limited bandwidth connection and you
435 don't want your transfer to use all of it (sometimes referred to as
436 "bandwith throttle").
438 Make curl transfer data no faster than 10 kilobytes per second:
440 curl --limit-rate 10K www.far-away-site.com
444 curl --limit-rate 10240 www.far-away-site.com
446 Or prevent curl from uploading data faster than 1 megabyte per second:
448 curl -T upload --limit-rate 1M ftp://uploadshereplease.com
450 When using the --limit-rate option, the transfer rate is regulated on a
451 per-second basis, which will cause the total transfer speed to become lower
452 than the given number. Sometimes of course substantially lower, if your
453 transfer stalls during periods.
457 Curl automatically tries to read the .curlrc file (or _curlrc file on win32
458 systems) from the user's home dir on startup.
460 The config file could be made up with normal command line switches, but you
461 can also specify the long options without the dashes to make it more
462 readable. You can separate the options and the parameter with spaces, or
463 with = or :. Comments can be used within the file. If the first letter on a
464 line is a '#'-letter the rest of the line is treated as a comment.
466 If you want the parameter to contain spaces, you must inclose the entire
467 parameter within double quotes ("). Within those quotes, you specify a
470 NOTE: You must specify options and their arguments on the same line.
472 Example, set default time out and proxy in a config file:
474 # We want a 30 minute timeout:
476 # ... and we use a proxy for all accesses:
477 proxy = proxy.our.domain.com:8080
479 White spaces ARE significant at the end of lines, but all white spaces
480 leading up to the first characters of each line are ignored.
482 Prevent curl from reading the default file by using -q as the first command
483 line parameter, like:
485 curl -q www.thatsite.com
487 Force curl to get and display a local help page in case it is invoked
488 without URL by making a config file similar to:
491 url = "http://help.with.curl.com/curlhelp.html"
493 You can specify another config file to be read by using the -K/--config
494 flag. If you set config file name to "-" it'll read the config from stdin,
495 which can be handy if you want to hide options from being visible in process
498 echo "user = user:passwd" | curl -K - http://that.secret.site.com
502 When using curl in your own very special programs, you may end up needing
503 to pass on your own custom headers when getting a web page. You can do
504 this by using the -H flag.
506 Example, send the header "X-you-and-me: yes" to the server when getting a
509 curl -H "X-you-and-me: yes" www.love.com
511 This can also be useful in case you want curl to send a different text in a
512 header than it normally does. The -H header you specify then replaces the
513 header curl would normally send. If you replace an internal header with an
514 empty one, you prevent that header from being sent. To prevent the Host:
515 header from being used:
517 curl -H "Host:" www.server.com
521 Do note that when getting files with the ftp:// URL, the given path is
522 relative the directory you enter. To get the file 'README' from your home
523 directory at your ftp site, do:
525 curl ftp://user:passwd@my.site.com/README
527 But if you want the README file from the root directory of that very same
528 site, you need to specify the absolute file name:
530 curl ftp://user:passwd@my.site.com//README
532 (I.e with an extra slash in front of the file name.)
536 The FTP protocol requires one of the involved parties to open a second
537 connction as soon as data is about to get transfered. There are two ways to
540 The default way for curl is to issue the PASV command which causes the
541 server to open another port and await another connection performed by the
542 client. This is good if the client is behind a firewall that don't allow
543 incoming connections.
545 curl ftp.download.com
547 If the server for example, is behind a firewall that don't allow connections
548 on other ports than 21 (or if it just doesn't support the PASV command), the
549 other way to do it is to use the PORT command and instruct the server to
550 connect to the client on the given (as parameters to the PORT command) IP
553 The -P flag to curl supports a few different options. Your machine may have
554 several IP-addresses and/or network interfaces and curl allows you to select
555 which of them to use. Default address can also be used:
557 curl -P - ftp.download.com
559 Download with PORT but use the IP address of our 'le0' interface (this does
560 not work on windows):
562 curl -P le0 ftp.download.com
564 Download with PORT but use 192.168.0.10 as our IP address to use:
566 curl -P 192.168.0.10 ftp.download.com
570 Get a web page from a server using a specified port for the interface:
572 curl --interface eth0:1 http://www.netscape.com/
576 curl --interface 192.168.1.10 http://www.netscape.com/
580 Secure HTTP requires SSL libraries to be installed and used when curl is
581 built. If that is done, curl is capable of retrieving and posting documents
582 using the HTTPS procotol.
586 curl https://www.secure-site.com
588 Curl is also capable of using your personal certificates to get/post files
589 from sites that require valid certificates. The only drawback is that the
590 certificate needs to be in PEM-format. PEM is a standard and open format to
591 store certificates with, but it is not used by the most commonly used
592 browsers (Netscape and MSIE both use the so called PKCS#12 format). If you
593 want curl to use the certificates you use with your (favourite) browser, you
594 may need to download/compile a converter that can convert your browser's
595 formatted certificates to PEM formatted ones. This kind of converter is
596 included in recent versions of OpenSSL, and for older versions Dr Stephen
597 N. Henson has written a patch for SSLeay that adds this functionality. You
598 can get his patch (that requires an SSLeay installation) from his site at:
599 http://www.drh-consultancy.demon.co.uk/
601 Example on how to automatically retrieve a document using a certificate with
604 curl -E /path/to/cert.pem:password https://secure.site.com/
606 If you neglect to specify the password on the command line, you will be
607 prompted for the correct password before any data can be received.
609 Many older SSL-servers have problems with SSLv3 or TLS, that newer versions
610 of OpenSSL etc is using, therefore it is sometimes useful to specify what
611 SSL-version curl should use. Use -3, -2 or -1 to specify that exact SSL
612 version to use (for SSLv3, SSLv2 or TLSv1 respectively):
614 curl -2 https://secure.site.com/
616 Otherwise, curl will first attempt to use v3 and then v2.
618 To use OpenSSL to convert your favourite browser's certificate into a PEM
619 formatted one that curl can use, do something like this (assuming netscape,
620 but IE is likely to work similarly):
622 You start with hitting the 'security' menu button in netscape.
624 Select 'certificates->yours' and then pick a certificate in the list
626 Press the 'export' button
628 enter your PIN code for the certs
630 select a proper place to save it
632 Run the 'openssl' application to convert the certificate. If you cd to the
633 openssl installation, you can do it like:
635 # ./apps/openssl pkcs12 -in [file you saved] -clcerts -out [PEMfile]
638 RESUMING FILE TRANSFERS
640 To continue a file transfer where it was previously aborted, curl supports
641 resume on http(s) downloads as well as ftp uploads and downloads.
643 Continue downloading a document:
645 curl -C - -o file ftp://ftp.server.com/path/file
647 Continue uploading a document(*1):
649 curl -C - -T file ftp://ftp.server.com/path/file
651 Continue downloading a document from a web server(*2):
653 curl -C - -o file http://www.server.com/
655 (*1) = This requires that the ftp server supports the non-standard command
656 SIZE. If it doesn't, curl will say so.
658 (*2) = This requires that the web server supports at least HTTP/1.1. If it
659 doesn't, curl will say so.
663 HTTP allows a client to specify a time condition for the document it
664 requests. It is If-Modified-Since or If-Unmodified-Since. Curl allow you to
665 specify them with the -z/--time-cond flag.
667 For example, you can easily make a download that only gets performed if the
668 remote file is newer than a local copy. It would be made like:
670 curl -z local.html http://remote.server.com/remote.html
672 Or you can download a file only if the local file is newer than the remote
673 one. Do this by prepending the date string with a '-', as in:
675 curl -z -local.html http://remote.server.com/remote.html
677 You can specify a "free text" date as condition. Tell curl to only download
678 the file if it was updated since yesterday:
680 curl -z yesterday http://remote.server.com/remote.html
682 Curl will then accept a wide range of date formats. You always make the date
683 check the other way around by prepending it with a dash '-'.
689 curl dict://dict.org/m:curl
690 curl dict://dict.org/d:heisenbug:jargon
691 curl dict://dict.org/d:daniel:web1913
693 Aliases for 'm' are 'match' and 'find', and aliases for 'd' are 'define'
694 and 'lookup'. For example,
696 curl dict://dict.org/find:curl
698 Commands that break the URL description of the RFC (but not the DICT
701 curl dict://dict.org/show:db
702 curl dict://dict.org/show:strat
704 Authentication is still missing (but this is not required by the RFC)
708 If you have installed the OpenLDAP library, curl can take advantage of it
709 and offer ldap:// support.
711 LDAP is a complex thing and writing an LDAP query is not an easy task. I do
712 advice you to dig up the syntax description for that elsewhere. Two places
713 that might suit you are:
715 Netscape's "Netscape Directory SDK 3.0 for C Programmer's Guide Chapter 10:
716 Working with LDAP URLs":
717 http://developer.netscape.com/docs/manuals/dirsdk/csdk30/url.htm
719 RFC 2255, "The LDAP URL Format" http://www.rfc-editor.org/rfc/rfc2255.txt
721 To show you an example, this is now I can get all people from my local LDAP
722 server that has a certain sub-domain in their email address:
724 curl -B "ldap://ldap.frontec.se/o=frontec??sub?mail=*sth.frontec.se"
726 If I want the same info in HTML format, I can get it by not using the -B
727 (enforce ASCII) flag.
729 ENVIRONMENT VARIABLES
731 Curl reads and understands the following environment variables:
733 http_proxy, HTTPS_PROXY, FTP_PROXY, GOPHER_PROXY
735 They should be set for protocol-specific proxies. General proxy should be
740 A comma-separated list of host names that shouldn't go through any proxy is
741 set in (only an asterisk, '*' matches all hosts)
745 If a tail substring of the domain-path for a host matches one of these
746 strings, transactions with that node will not be proxied.
749 The usage of the -x/--proxy flag overrides the environment variables.
753 Unix introduced the .netrc concept a long time ago. It is a way for a user
754 to specify name and password for commonly visited ftp sites in a file so
755 that you don't have to type them in each time you visit those sites. You
756 realize this is a big security risk if someone else gets hold of your
757 passwords, so therefor most unix programs won't read this file unless it is
758 only readable by yourself (curl doesn't care though).
760 Curl supports .netrc files if told so (using the -n/--netrc and
761 --netrc-optional options). This is not restricted to only ftp,
762 but curl can use it for all protocols where authentication is used.
764 A very simple .netrc file could look something like:
766 machine curl.haxx.se login iamdaniel password mysecret
770 To better allow script programmers to get to know about the progress of
771 curl, the -w/--write-out option was introduced. Using this, you can specify
772 what information from the previous transfer you want to extract.
774 To display the amount of bytes downloaded together with some text and an
777 curl -w 'We downloaded %{size_download} bytes\n' www.download.com
779 KERBEROS4 FTP TRANSFER
781 Curl supports kerberos4 for FTP transfers. You need the kerberos package
782 installed and used at curl build time for it to be used.
784 First, get the krb-ticket the normal way, like with the kauth tool. Then use
785 curl in way similar to:
787 curl --krb4 private ftp://krb4site.com -u username:fakepwd
789 There's no use for a password on the -u switch, but a blank one will make
790 curl ask for one and you already entered the real password to kauth.
794 The curl telnet support is basic and very easy to use. Curl passes all data
795 passed to it on stdin to the remote server. Connect to a remote telnet
796 server using a command line similar to:
798 curl telnet://remote.server.com
800 And enter the data to pass to the server on stdin. The result will be sent
801 to stdout or to the file you specify with -o.
803 You might want the -N/--no-buffer option to switch off the buffered output
804 for slow connections or similar.
806 Pass options to the telnet protocol negotiation, by using the -t option. To
807 tell the server we use a vt100 terminal, try something like:
809 curl -tTTYPE=vt100 telnet://remote.server.com
811 Other interesting options for it -t include:
813 - XDISPLOC=<X display> Sets the X display location.
815 - NEW_ENV=<var,val> Sets an environment variable.
817 NOTE: the telnet protocol does not specify any way to login with a specified
818 user and password so curl can't do that automatically. To do that, you need
819 to track when the login prompt is received and send the username and
820 password accordingly.
822 PERSISTANT CONNECTIONS
824 Specifying multiple files on a single command line will make curl transfer
825 all of them, one after the other in the specified order.
827 libcurl will attempt to use persistant connections for the transfers so that
828 the second transfer to the same host can use the same connection that was
829 already initiated and was left open in the previous transfer. This greatly
830 decreases connection time for all but the first transfer and it makes a far
831 better use of the network.
833 Note that curl cannot use persistant connections for transfers that are used
834 in subsequence curl invokes. Try to stuff as many URLs as possible on the
835 same command line if they are using the same host, as that'll make the
836 transfers faster. If you use a http proxy for file transfers, practicly
837 all transfers will be persistant.
841 For your convenience, we have several open mailing lists to discuss curl,
842 its development and things relevant to this. Get all info at
843 http://curl.haxx.se/mail/. The lists available are:
847 Users of the command line tool. How to use it, what doesn't work, new
848 features, related tools, questions, news, installations, compilations,
849 running, porting etc.
853 Developers using or developing libcurl. Bugs, extensions, improvements.
857 Low-traffic. Only announcements of new public versions.
861 Using the curl functions in PHP. Everything curl with a PHP angle. Or PHP
866 Receives notifications on all CVS commits done to the curl source module.
867 This can become quite a large amount of mails during intense development,
868 be aware. This is for us who like email...
872 Receives notifications on all CVS commits done to the curl www module
873 (basicly the web site). This can become quite a large amount of mails
874 during intense changing, be aware. This is for us who like email...
876 Please direct curl questions, feature requests and trouble reports to one of
877 these mailing lists instead of mailing any individual.