now runs fine.

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

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.

  handle that is part of a multi handle first removes the handle from the
  stack.

- Added CURLOPT_SSL_SESSIONID_CACHE and --no-sessionid to disable SSL
  session-ID re-use on demand since there obviously are broken servers out
  there that misbehave with session-IDs used.

Winsock.

cache within the multi handle.

used the default port. He was right. I fixed the problem and added the test
cases 521, 522 and 523 to verify the fix.

the failed connect "immediately".

different values for it...

file got a Last-Modified: header written to the data stream, corrupting the
actual data. This was because some conditions from the previous FTP code was
not properly brought into the new FTP code. I fixed and I added test case 520
to verify. (This bug was introduced in 7.13.1)

The tag 'before_ftp_statemachine' was set just before this commit in case
of future need.

to allow the contents of the env var decide the file name.

connection.

it works, as it has proved to not work in some cases (like on Tor Arntsen's
AIX 5100-06 xlc 5.0 --disable-shared runs).

it actually can run and test the FD_SETSIZE stuff it is meant to test

systems that can't run it fine.

it resolving nicely

no fixed port numbers in use anymore. Starting now, the default ports the
servers use are 8990 - 8993. There's no option to modify these yet, but
changing the $base option in the top of the runtests.pl script.