cache grow a bit too much, beyond the normal 4 * easy_handles.

  several FTP-SSL test cases fail when we build libcurl with NSS for TLS/SSL:
  http://curl.haxx.se/bug/view.cgi?id=1705802

when CURLOPT_HTTP200ALIASES is used to avoid the problem mentioned below is
not very nice if the client wants to be able to use _either_ a HTTP 1.1
server or one within the aliases list... so starting now, libcurl will
simply consider 200-alias matches the to be HTTP 1.0 compliant.

libcurls, which turned out to be the 25-nov-2006 change which treats HTTP
responses without Content-Length or chunked encoding as without bodies. We
now added the conditional that the above mentioned response is only without
body if the response is HTTP 1.1.

  CURLMOPT_TIMERFUNCTION callback option.

  when CURLM_CALL_MULTI_PERFORM is returned from curl_multi_socket*/perform,
  to make applications using only curl_multi_socket() to properly function
  when adding easy handles "on the fly". Bug report and test app provided by
  Michael Wallner.

for every year is giving us too many files! I also split out the changes
from 2006 from CHANGES to CHANGES.0 now.

Reduce the scope of some variables.

looking for a C++ preprocessor on libtool-using projects" with the factory-
installed libtool version on Mac OS X.

the default port numbers, allowing more than one test suite to run
simultaneously on the same host.

since it then inits libgcrypt and libgcrypt is being evil and EXITS the
application if it fails to get a fine random seed. That's really not a nice
thing to do by a library.

been removed from a multi handle, and then fixed another flaw that prevented
curl_easy_duphandle() to work even after the first fix - the handle was
still marked as using the multi interface.

since it easy-handle related and not connection-related.

moves and re-arranges how range/resume is setup and freed.

was 16385 bytes (16K+1) and it turned out we didn't properly always "suck
out" all data from libssh2. The effect being that libcurl would hang on the
socket waiting for data when libssh2 had in fact already read it all...

the CURLOPT_RESUME_FROM or CURLOPT_RANGE options and an existing connection
in the connection cache is closed to make room for the new one when you call
curl_easy_perform(). It would then wrongly free range-related data in the
connection close funtion.

would get from a torture test.

Wait for child processes to die to avoid creating zombies.

can/will be used as it then makes the common cases save 16KB of data for each
easy handle that isn't used for pipelining.

to guarantee against it ever being valid.

using custom timeout values.