change options on an SSL-enabled connection between requests.

related stuff within HAVE_OPENSSL_ENGINE_H and we don't make any private
typedef or similar if the header is missing...

header is used, we must wait for a 100-code (or timeout), before we send the
data. The timeout is merely 1000 ms at this point. We may have reason to set
a longer timeout in the future.

only allocating the scratch memory buffer once it is needed and not always
in the handle.

"username" will cause libcurl to prompt for password. Bryan Kemp noticed.

test case 136 is added for this

or not

regular transfer process. This required some new tweaks, like for example
we need to be able to tell the tranfer loop to not chunky-encode uploads
while we're transferring the rest of the request...

read callback, and thus won't put a lot of stress on the request sending
code (which currently does an ugly loop).

connectdata struct instead, and is no longer modified within the 'set' struct
as previously (which was a really BAAAD thing).

proper CURLcode. The default timeout for reading one response is now also
possible to change while running.

for storage and retrieval of private data in the curl handle.

ConnectBits where the other bools already are

size of the uploaded file is unknown.

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.

badly assumed header, or we think that parts of the buffer is a bad header
and the rest is treated as a normal body part

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

case 306 added to verify that we do right

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.

weren't used anyway and mostly caused confusion

the initial connect to "come through".

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

the easy interface, it CANNOT be used by a mixture.

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

variables, conditions and things.

message is supposed to be ignored.

sized buffer that may be passed to a write callback

we need to point to user-provided fd_sets