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!

verifies the bug fix in #1757328.

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

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

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.

openssh

case 614.
Allow SFTP quote commands chmod, chown, chgrp to set a value of 0.

and added tests 290 and 291 to check.

test case 288 to verify it.

supports only ftps:// URLs with --ftp-ssl-control specified, which
implicitly encrypts the control channel but not the data channels.  That
allows stunnel to be used with an unmodified ftp server in exactly the
same way that the test https server is set up.
Added test case 400 as a basic FTPS test.

  header, you got _two_ User-Agent headers in the CONNECT request...! Added
  test case 287 to verify the fix.

something went wrong like it got a bad response code back from the server,
libcurl would leak memory. Added test case 538 to verify the fix.

I also noted that the connection would get cached in that case, which
doesn't make sense since it cannot be re-use when the authentication has
failed. I fixed that issue too at the same time, and also that the path
would be "remembered" in vain for cases where the connection was about to
get closed.

when more than FD_SETSIZE file descriptors are open.
This means that if for any reason we are not able to
open more than FD_SETSIZE file descriptors then test
518 should not be run.

test 537 is all about testing libcurl functionality
when the system has nearly exhausted the number of
free file descriptors. Test 537 will try to run with
very few free file descriptors.

case when 401 or 407 are returned, *IF* no auth credentials have been given.
The CURLOPT_FAILONERROR option is not possible to make fool-proof for 401
and 407 cases when auth credentials is given, but we've now covered this
somewhat more.

You might get some amounts of headers transferred before this situation is
detected, like for when a "100-continue" is received as a response to a
POST/PUT and a 401 or 407 is received immediately afterwards.

Added test 281 to verify this change.

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

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.