curl/tests/data/test538

<testcase>
<info>
<keywords>
FTP
FAILURE
</keywords>
</info>
# Server-side
<reply>
</reply>

# Client-side
<client>
<server>
ftp
</server>
# NOTE that we use the 504 tool for this case
<tool>
lib504
</tool>
 <name>
FTP multi-interface download, failed login: PASS not valid
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/538
</command>
<file name="log/ftpserver.cmd">
REPLY PASS 314 bluah you f00l!
</file>
</client>

# Verify data after the test has been "shot"
<verify>
# ok, the error code here is supposed to be 100 for the fine case since
# that's just how lib504.c is written
<errorcode>
100
</errorcode>
<protocol>
USER anonymous
PASS curl_by_daniel@haxx.se
</protocol>
</verify>
</testcase>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`<testcase>`
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. 2006-12-11 04:32:58 -05:00			`<info>`
			`<keywords>`
			`FTP`
			`FAILURE`
			`</keywords>`
			`</info>`
			`# Server-side`
			`<reply>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
			`# NOTE that we use the 504 tool for this case`
			`<tool>`
			`lib504`
			`</tool>`
			`<name>`
			`FTP multi-interface download, failed login: PASS not valid`
			`</name>`
			`<command>`
			`ftp://%HOSTIP:%FTPPORT/538`
			`</command>`
			`<file name="log/ftpserver.cmd">`
			`REPLY PASS 314 bluah you f00l!`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`# ok, the error code here is supposed to be 100 for the fine case since`
			`# that's just how lib504.c is written`
			`<errorcode>`
			`100`
			`</errorcode>`
			`<protocol>`
			`USER anonymous`
			`PASS curl_by_daniel@haxx.se`
			`</protocol>`
			`</verify>`
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`</testcase>`