(http://curl.haxx.se/bug/view.cgi?id=1776235) about ftp requests with NOBODY
on a directory would do a "SIZE (null)" request. This is now fixed and test
case 1000 was added to verify.

range. They are about FTP but the 100-199 range is full.

HTTP PUT using Digest authentication. Test case 5320 and 5322 were also
added to verify the functionality.

after 7.16.2. This is much due to the different treatment file:// gets
internally, but now I added test 231 to make it less likely to happen again
without us noticing!

some few internal identifiers to avoid conflicts, which could be useful on
other platforms.

to occur in a couple of tests.

verifies the bug fix in #1757328.

from the test server code as they served no real purpose. The test server is
here to serve for the test cases, not to attempt to function as a real server!

keys that small.

really reduce security since in the common case of a daily automated build
the keys are only used for a single test run lasting a few minutes before
being deleted.

a new directory listing format that newer libssh2's can provide.  This
is probably NOT sufficient to handle all directory listing formats that
server's can provide and should be revisited.

can take advantage of it however they see fit!

Regev on the libcurl mailing list on 10 Jul 2007, converted to a test case.

really hard if the test server can't be resolved (like for ::1 ipv6)

it 10 seconds delay after 11 attempts

added go_sleep() to util.c.

using one of the so-called 'right' time zones that take into account
leap seconds, which causes the tests to fail (as reported by
Daniel Black in bug report #1745964).

of the patch he suggested.  Added his test case as test289 to verify.

file.c, but the debug interface was missing.  This adds the routines needed
to make the memory debuging work for fdopen().

chunked encoding (that also lacks "Connection: close"). It now simply
assumes that the connection WILL be closed to signal the end, as that is how
RFC2616 section 4.4 point #5 says we should behave.

tool reports and it was indeed a legitimate one and it is one fixed. It was
a use of a share without doing the proper locking first.

from the #1739100 bug report

disable test 351 by default by I add the test case anyway to make it easier
to work on this problem in the future.

sftp tests run fine on gentoo

keys the first time (which can take a while on a slow or loaded host).
Enforce a longer startup wait time for the ssh client SOCKS server, too.
Check for an error code from startnew() when starting any server.