updates

 - download

 - authentication

 - kerberos security

 - PORT or PASV

 - active/passive using PORT, EPRT, PASV or EPSV

 - single file size information (compare to HTTP HEAD)

 - 'type=' URL support

 - dir listing

   The configure script always tries to find a working SSL library unless

   explicitly told not to. If you have OpenSSL installed in the default search

   path for your compiler/linker, you don't need to do anything special. If

   you have OpenSSL installed in e.g /usr/local/ssl, you can run configure

   like:

   you have OpenSSL installed in /usr/local/ssl, you can run configure like:

	./configure --with-ssl

	./configure --with-ssl=/opt/OpenSSL

   If you insist on forcing a build *without* SSL support, even though you may

   have it installed in your system, you can run configure like this:

   If you insist on forcing a build without SSL support, even though you may

   have OpenSSL installed in your system, you can run configure like this:

        ./configure --without-ssl

   If you have OpenSSL installed, but with the libraries in one place and the

   header files somewhere else, you'll have to set the LDFLAGS and CPPFLAGS

   header files somewhere else, you have to set the LDFLAGS and CPPFLAGS

   environment variables prior to running configure.  Something like this

   should work:

     LIBS=-lRSAglue -lrsaref

     (as suggested by Doug Kaufman)

   KNOWN PROBLEMS

   KNOWN PROBLEMS (these ones should not happen anymore)

     If you happen to have autoconf installed, but a version older than 2.12

     you will get into trouble. Then you can still build curl by issuing these

   MORE OPTIONS

     Remember, to force configure to use the standard cc compiler if both

     cc and gcc are present, run configure like

     To force configure to use the standard cc compiler if both cc and gcc are

     present, run configure like

       CC=cc ./configure

         or

       ./configure --with-krb4=/usr/athena

     If your system support shared libraries, but you want to built a static

     version only, you can disable building the shared version by using:

       ./configure --disable-shared

     If you're a curl developer and use gcc, you might want to enable more

     debug options with the --enable-debug option.

  systems. While not being the main develop target, a fair share of curl users

  are win32-based.

  Some documentation in this archive will be tricky to read for Windows

  people, as they come in unix-style man pages. You can either download a

  freely available nroff binary for win32 (*pointers appriciated*), convert

  the files into plain-text on your neighbor's unix machine or run over to the

  curl web site and view them as plain HTML.

  The unix-style man pages are tricky to read on windows, so therefore are all

  those pages also converted to HTML and those are also included in the

  release archives.

  The main curl.1 man page is "built-in". Use a command line similar to this

  in order to extract a separate text file:

  The main curl.1 man page is also "built-in" in the command line tool. Use a

  command line similar to this in order to extract a separate text file:

        curl -M >manual.txt

  Download all the libcurl man pages in HTML format using the link on the

  bottom of this page:

        http://curl.haxx.se/libcurl/c/