don't expect fully qualified names we need to cut them off at the first dot.

of them can be completetly removed though...

cache within the multi handle.

  while not fixing things very nicely, it does make the SOCKS5 proxy
  connection slightly better as it now acknowledges the timeout for connection
  and it no longer segfaults in the case when SOCKS requires authentication
  and you did not specify username:password.

name resolves. It could get stuck in the wrong state.

allow applications to set their own socket options.

properly if you removed a "live" handle from a multi handle with
curl_multi_remove_handle().

code when doing pure ipv6 EPRT connections.

command on subsequent requests on a re-used connection unless it has to.

files in the root directory.

send the whole request at once, even though the Expect: header was disabled
by the application. An effect of this change is also that small (< 1024
bytes) POSTs are now always sent without Expect: header since we deem it
more costly to bother about that than the risk that we send the data in
vain.

CURLOPT_NOBODY is set true. PREQUOTE is then run roughly at the same place
in the command sequence as it would have run if there would've been a
transfer.

on a persistent connection and allowed the first to use that header, you
could not disable it for the second request.

if the header "Transfer-Encoding: chunked" was set by the application.
http://curl.haxx.se/bug/view.cgi?id=1531838

an unknown error number on glibc systems.
http://curl.haxx.se/bug/view.cgi?id=1532289

formposts work exactly the way you want it (and the way you'd assume it
works)

control and data connection, as the existing --ftp-ssl option only requests
it.

tool option named --ftp-alternative-to-user. It provides a mean to send a
particular command if the normal USER/PASS approach fails.

we did wrong and patched it: When nodes were removed from the splay tree,
and we didn't properly remove it from the splay tree when an easy handle was
removed from a multi stack and thus we could wrongly leave a node in the
splay tree pointing to (bad) memory.

for FTP ASCII transfers.

string comparisons on the path which is incorrect and provided a patch that
fixes this. I edited test case 8 to include details that test for this.

the crash was that libcurl internally was a bit confused about who owned the
DNS cache at all times so if you created an easy handle that uses a shared
DNS cache and added that to a multi handle it would crash. Now we keep more
careful internal track of exactly what kind of DNS cache each easy handle
uses: None, Private (allocated for and used only by this single handle),
Shared (points to a cache held by a shared object), Global (points to the
global cache) or Multi (points to the cache within the multi handle that is
automatically shared between all easy handles that are added with private
caches).

Proxy-Connection: header when using a proxy and not doing CONNECT.

bugfixes

(serialise) a previously built formpost (as with curl_formadd()).

curl_socket_t is unsigned (like Windows) that could cause it to wrongly
return a max fd of -1.

CURLOPT_MAX_RECV_SPEED_LARGE that limit tha maximum rate libcurl is allowed
to send or receive data. This kind of adds the the command line tool's
option --limit-rate to the library.

The rate limiting logic in the curl app is now removed and is instead
provided by libcurl itself. Transfer rate limiting will now also work for -d
and -F, which it didn't before.