--vernum

  them all use the same (hopefully correct) logic to make it less error-prone
  and easier to introduce library-wide where it should be used.

ca-bundle.crt file as outdated and in need for replacement by anyone who wants
to verify modern peers as the one we have is from year 2000!

Improve handling of boundary conditions for huge requests.

Disable "swsbounce" mode when the received request
isn't for the same test and part number.

the whole 150000+ bytes struct, and also removing an equally big
additional buffer for pipelining treatment.

  use of the "is_in_pipeline" struct field.

HTTPS sites with OpenSSL-enabled libcurl (and pthreads) and thus do the
thread-locking and things openssl-style.

install process.  Note that mkinstalldirs appears to be used only
in some configurations.

which are deprecated in recent OpenSSH versions but are current for SunSSH.

  "HttpOnly" feature introduced by Microsoft and apparently also supported by
  Firefox: http://msdn2.microsoft.com/en-us/library/ms533046.aspx . HttpOnly
  is now supported when received from servers in HTTP headers, when written to
  cookie jars and when read from existing cookie jars.

  the SingleRequest one to make pipelining better. It is a bit tricky to keep
  them in the right place, to keep things related to the actual request or to
  the actual connection in the right place.

51.Kevin Reed's reported problem with a proxy when doing CONNECT and it
  wants NTLM and close the connection to the initial CONNECT response:
  http://curl.haxx.se/bug/view.cgi?id=1879375

added curl.res to clean target.

  crash!

  working on other IP-addresses or port numbers.

release but hopefully they'll all be fixed in 7.18.1...

pipelining. Broken connection is not restored and we get into infinite
loop. It happens because of wrong is_in_pipeline values.

  (http://curl.haxx.se/bug/view.cgi?id=1879375) which describes how libcurl
  got lost in this scenario: proxy tunnel (or HTTPS over proxy), ask to do any
  proxy authentication and the proxy replies with an auth (like NTLM) and then
  closes the connection after that initial informational response.

  libcurl would not properly re-initialize the connection to the proxy and
  continue the auth negotiation like supposed. It does now however, as it will
  now detect if one or more authentication methods were available and asked
  for, and will thus retry the connection and continue from there.

- I made the progress callback get called properly during proxy CONNECT.