updated

 - follow redirects

 - custom HTTP request

 - cookie get/send

 - understands the netscape cookie file

 - understands the netscape cookie file format

 - custom headers (that can replace/remove internally generated headers)

 - custom user-agent string

 - custom referer string

 - proxy authentication

 - time conditions

 - via http-proxy

 - specify interface device/port

HTTPS (*1)

 - (all the HTTP features)

FTP

 - download

 - authentication

 - kerberos security

 - PORT or PASV

 - single file size information (compare to HTTP HEAD)

 - 'type=' URL support

        - Ultrix

        - SINIX-Z v5

        - Alpha Tru64 v5.0 5.1

        - Alpha DEC OSF 4

        - Alpha Digital UNIX v3.2

        - Alpha FreeBSD 4.1

        - Alpha Linux 2.2.16

        - Alpha Tru64 v5.0 5.1

        - HP-PA HP-UX 9.X 10.X 11.X

        - MIPS IRIX 6.2, 6.5

        - Power AIX 4.2, 4.3.1, 4.3.2

        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

 * Move non-URL related functions that are used by both the lib and the curl

   application to a separate "portability lib".

 * Add support for other languages than C (not important). C++ and perl comes

   to mind. Python?

 * Add support for other languages than C. C++ and perl comes to mind. Python?

 * Improve the -K config file parser.

 * Improve the -K config file parser (the parameter following the flag should

   be possible to get specified *exactly* as it is done on a shell command

   line).

 * rtsp:// support -- "Real Time Streaming Protocol" (RFC 2326)

   started in October 1999 but halted again since it proved more work than we

   thought. It is still a good idea to implement though.

 * HTTP Pipelining/persistant connections

 - We should introduce HTTP "pipelining". Curl could be able to request for

   several HTTP documents in one connect. It would be the beginning for

   supporing more advanced functions in the future, like web site

   mirroring. This will require that the urlget() function supports several

   documents from a single HTTP server, which it doesn't today.

 - When curl supports fetching several documents from the same server using

   pipelining, I'd like to offer that function to the command line. Anyone has

   a good idea how? The current way of specifying one URL with the output sent

   to the stdout or a file gets in the way. Imagine a syntax that supports

   "additional documents from the same server" in a way similar to:

     curl <main URL> --more-doc <path> --more-doc <path>

   where --more-doc specifies another document on the same server. Where are

   the output files gonna be put and how should they be named? Should each

   "--more-doc" parameter require a local file name to store the result in?

   Like "--more-file" as in:

     curl <URL> --more-doc <path> --more-file <file>

 * Authentication: NTLM. It would be cool to support that MS crap called NTLM

   authentication. MS proxies and servers sometime require that. Since that

   protocol is a proprietary one, it involves reverse engineering and network

   sniffing. This should however be a library-based functionality. There are a

   few different efforts "out there" to make open source HTTP clients support

   this and it should be possible to take advantage of other people's hard

   work.

 * RFC2617 compliance, "Digest Access Authentication"

   A valid test page seem to exist at:

 * Make curl capable of verifying the server's certificate when connecting

   with HTTPS://.

 * Kerberos-FTP, krb4-ftp

.\" nroff -man curl.1

.\" Written by Daniel Stenberg

.\"

.TH curl 1 "15 August 2000" "Curl 7.3" "Curl Manual"

.TH curl 1 "20 September 2000" "Curl 7.3" "Curl Manual"

.SH NAME

curl \- get a URL with FTP, TELNET, LDAP, GOPHER, DICT, FILE, HTTP or

HTTPS syntax.

(HTTP)

Include the HTTP-header in the output. The HTTP-header includes things

like server-name, date of the document, HTTP-version and more...

.IP "--interface <name>"

Perform an operation using a specified interface. You can enter interface

name, IP address or host name. An example could look like:

.B "curl --interface eth0:1 http://www.netscape.com/"

.IP "-I/--head"

(HTTP/FTP)

Fetch the HTTP-header only! HTTP-servers feature the command HEAD

which this uses to get nothing but the header of a document. When used

on a FTP file, curl displays the file size only.

.IP "--krb4 <level>"

(FTP) Enable kerberos4 authentication and use. The level must be entered and

should be one of 'clear', 'safe', 'confidential' or 'private'. Should you use

a level that is not one of these, 'private' will instead be used.

.IP "-K/--config <config file>"

Specify which config file to read curl arguments from. The config

file is a text file in which command line arguments can be written

 - Fred Noz <FNoz@siac.com>

 - Caolan McNamara <caolan@csn.ul.ie>

 - Albert Chin-A-Young <china@thewrittenword.com>

 - Stephen Kick <skick@epicrealm.com>

 - Martin Hedenfalk <mhe@stacken.kth.se>

 - Richard Prescott

.SH WWW

http://curl.haxx.se