server configured in the system, the ares_init() call fails and thus
  curl_easy_init() fails as well. This causes weird effects for people who use
  numerical IP addresses only.

an app can use to let libcurl only connect to a remote host and then extract
the socket from libcurl. libcurl will then not attempt to do any transfer at
all after the connect is done.

due to the use of the static variable for sigsetjmp()

curl tool with --local-port. Plain and simply set the range of ports to bind
the local end of connections to. Implemented on to popular demand.

Not extensively tested. Please let me know how it works.

of the system instead of depending on what particular systems we think need
various headers

fact equal to a blank one according to the spec.

Tried to make some of the wording a bit more consistent.

the latest features and protocols that libcurl supports and has a minor fix to
better deal with the obscure case where someone has more than one libcurl
installed at the same time.

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.

into a counter, and thus you can now do multiple curl_global_init() and you
are then supposed to do the same amount of calls to curl_global_cleanup().
Bryan also updated the docs accordingly.

interface

cleanups of this man page. The lengthy description has now also been removed
from curl/multi.h since it immediately got tedious to maintain the info on
two places when I did major updates...

curl_easy_init() if you don't call curl_global_init() explicitly in your app

now to enable them to get added as web pages easier, they are not ready
for anything "real" just yet.

run that might be needed only for building libcurl.

fix CONNECT to a proxy that disconnects during the auth phase

issues in the code.