From 88c8d72a214864952b6d1c2347b6c3f5b7d69e84 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 11 Dec 2006 09:32:58 +0000 Subject: Alexey Simak found out that when doing FTP with the multi interface and 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. --- tests/data/test538 | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 tests/data/test538 (limited to 'tests/data/test538') diff --git a/tests/data/test538 b/tests/data/test538 new file mode 100644 index 000000000..6ad2aac13 --- /dev/null +++ b/tests/data/test538 @@ -0,0 +1,42 @@ + + +FTP +FAILURE + + +# Server-side + + + +# Client-side + + +ftp + +# NOTE that we use the 504 tool for this case + +lib504 + + +FTP multi-interface download, failed login: PASS not valid + + +ftp://%HOSTIP:%FTPPORT/538 + + +REPLY PASS 314 bluah you f00l! + + + +# Verify data after the test has been "shot" + +# ok, the error code here is supposed to be 100 for the fine case since +# that's just how lib504.c is written + +100 + + +USER anonymous +PASS curl_by_daniel@haxx.se + + -- cgit v1.2.3