provided for bug report #1871269, fixed on Jan 14 2008 before the 7.18.0
release.

previously had a number of flaws, perhaps most notably when an application
fired up N transfers at once as then they wouldn't pipeline at all that
nicely as anyone would think... Test case 530 was also updated to take the
improved functionality into account.

already worked for FTP:// URLs

(http://curl.haxx.se/bug/view.cgi?id=1850730) I wrote up test case 552. The
test is doing a 70K POST with a read callback and an ioctl callback over a
proxy requiring Digest auth. The test case code is more or less identical to
the test recipe code provided by Spacen Jasset (who submitted the bug report).

A failed attempt to repeat bug report #1850730 (ie the test works fine).

callback) over a proxy when NTLM is used as auth with the proxy. The bug
also concerned Digest and was limited to using callback only. Spacen worked
with us to provide a useful patch. I added the test case 547 and 548 to
verify two variations of POST over proxy with NTLM.

is supposed to repeat the bug report "NTLM proxy authentication with
CURLOPT_READDATA seems broken." posted on the curl-library mailing list on dec
3 2007.

present when enabled by on option which isn't done by default (and isn't even
available for the curl app atm)

when builddir is different from srcdir.

source tree 'tests' directory

protocols listed in curl --version

failed one using the multi interface

test harness supports.

found by Michal Marek.

Disable valgrind in test case 1004 due to a libtool bug.

Tests 35, 544 545 added: binary data POSTs.

Added test cases 2002 and 2003 (the latter disabled for now)

same easy handle
Fixed the filecheck: make target to work outside the source tree

risk of failures.

This happened because the tftp code always uncondionally did a bind()
without caring if one already had been done and then it failed. I wrote a
test case (1009) to verify this, but it is a bit error-prone since it will
have to pick a fixed local port number and since the tests are run on so
many different hosts in different situations I add it in disabled state.

Added test case 1008 to verify. Note that #47 is still there.