2006. It turned out we wrongly assumed that the connection cache was present
when tearing down a connection.

multi interface, but I could also repeat it doing multiple sequential ones
with the easy interface. Using Ciprian's test case, I could fix it.

Add failure checking for servers when fork()ed.

Use same code path in 'stopserver' when called with a single or multiple pids.

CURLOPT_VERBOSE set to non-zero, you still got a few debug messages from the
SSL handshake. This is now stopped.

wrong error message in the error message buffer.

This was possible on debug c-ares enabled builds when both CURL_MEMDEBUG
and CARES_MEMDEBUG environment variables were set. Leading to a file handle
leak even when both variables had the same value, and wierd test suite
results when different.

KNOWN_BUGS #25, which happens when a proxy closes the connection when
libcurl has sent CONNECT, as part of an authentication negotiation. Starting
now, libcurl will re-connect accordingly and continue the authentication as
it should.

a fatal bug so we must require 1.3.2 to get flawless functionality with c-ares.

behaviour some versions of IRIX exhibit of committing suicide on big
mallocs instead of just returning a friendly null pointer

fix closing of fd's when limit is reached