to the CURLOPT_DEBUGFUNCTION callback has been fixed (it was erroneously
included as part of the header).  A message was also added to the
command line tool to show when data is being sent, enabled when
--verbose is used.

for it

function, this is only meant to allow easier tracking of the internal handle's
state and what sockets they use. Only for research and development.

to a multi stack will cause CURLM_BAD_EASY_HANDLE to get returned.

and while doing so it became apparent that the current timeout system for
the socket API really was a bit awkward since it become quite some work to
be sure we have the correct timeout set.

Jeff then provided the new CURLMOPT_TIMERFUNCTION that is yet another
callback the app can set to get to know when the general timeout time
changes and thus for an application like hiperfifo.c it makes everything a
lot easier and nicer. There's a CURLMOPT_TIMERDATA option too of course in
good old libcurl tradition.

anymore

case 535 and it now runs fine. Again a problem with the pipelining code not
taking all possible (error) conditions into account.

In this way 304 tests out of 304 reported OK.

now runs fine.

but that worked nicely in 7.15.5. I converted it into test case 532 and
fixed the problem.

transfer support

would crash if a bad function sequence was used when shutting down after
using the multi interface (i.e using easy_cleanup after multi_cleanup) so
precautions have been added to make sure it doesn't any more - test case 529
was added to verify.

jar has died and we now instead point out our own version of that

Vista (_WIN32_WINNT >= 0x0600)

it now will read the full data sent from servers. The SOCKS-related code was
also moved to the new lib/socks.c source file.

empty password or no password at all. Test case 278 and 279 were added to
verify.

it basically was that we didn't remove the current connection from the pipe
list when following a redirect. Also in this commit: several cases of
additional debug code for debug builds helping to check and track down some
signs of run-time trouble.

currently fits in the cache, to make the cache work better especially for
pipelining cases but also for "mere" (persistent) connection re-use.