typecast in the curl tool leading to a crash with (64bit?) VS2005 (at least)
since the struct timeval field tv_sec is an int while time_t is 64bit.

about what sockets to wait for what action on

CURLOPT_TIMEOUT, the _longer_ time would wrongly be used for the SSL
connection time-out!

code rearrange to fit the future better.

fork support for cooler tests

ordinary test suite. Also removed the perror() calls and instead made the
logging output the errno code to ease error tracking using logs.

and it should break most other systems. The "funny" part is that debian
actually have a 'stunnel' setup to simulate stunnel v3 but it breaks our own
stunnel-version-detect-and-adjust-to-it system.

Added initial support for optionally running servers with fork support.

read one byte at a time...

  This happens because the multi-pass code abuses the redirect following code
  for doing multiple requests, and when we following redirects to an absolute
  URL we must use the newly specified port and not the one specified in the
  original URL. A proper fix to this would need to separate the negotiation
  "redirect" from an actual redirect.

     documented or pushed for.

for not returning a value from a non-void function (even though the code
never actually reached that point before)

attempt to silence picky compilers when assigning data pointers to a function
pointer variable

unsigned chars

hosts

(http://curl.haxx.se/mail/lib-2006-02/0154.html) by adding the NTLM hash
function in addition to the LM one and making some other adjustments in the
order the different parts of the data block are sent in the Type-2 reply.
Inspiration for this work was taken from the Firefox NTLM implementation.

I edited the existing 21(!) NTLM test cases to run fine with these news. Due
to the fact that we now properly include the host name in the Type-2 message
the test cases now only compare parts of that chunk.

if any use of such a function slip through

occurred when asking libcurl to follow HTTP redirects and the original URL had
more than one question mark (?). Added test case 276 to verify.