size of the uploaded file is unknown.

CURLOPT_CONNECTTIMEOUT was used and provided a fix.

counter so that the caller needs to decrease that counter when done with
the returned data.

If compiled with MALLOCDEBUG I've added some extra checking that the counter
is decreased before a handle is closed etc.

strnequal() when the third argument was strlen(first argument) anyway.
This makes it less prone to errors. (Slightly edited by me)

when given in the curl_easy_setopt() and then parse them all on the first
curl_easy_perform() call instead.

you set CURLOPT_PROXY to "".

environment variables or anything. Setting it to NULL disables proxy as well,
but allows the environment variables to kick in and be used.

uninitialized variable.

adjustments and possibly some improvments to feature all those things we
could possibly want from this.

when talking to a IPv6-server using IPv6 IP address only.

proceed fine with the already existing options, just having a different
internal library default for capath.

working for "IPv6 enabled" libcurls yet, but should be pretty easy for
someone to adjust.

the initial connect to "come through".

This should work fine for connect and for FTP-PASV connects. Needs massive
testing.

of time!

it to NULL and then use the internal default instead. It will always be
a function to call.

for receiving data from the network. It is meant as a hint, not as a forced
limit.

  faster on Windows when removing the 1 microsecond timeout.

case a timeout is set. This seems to work. God knows if it is good enough
or what kind of side-effects we introduce here and now.

I'll close my eyes and cross my fingers. Hard.

we might actually re-use a connection to a different host, when using proxies!

This was what bug report #558888 was all about.

any name resolved data in any curl handle struct. That way, we won't mind
if the cache entries are pruned for the next time we need them. We'll just
resolve them again instead.

This changes the Curl_resolv() proto. It modifies the SessionHandle struct
but perhaps most importantly, it'll make the internals somewhat dependent
on the DNS cache not being disabled as that will cripple operations somewhat.
Especially for persistant connections.

from the host names before comparing