curl/tests/data/test1096

<testcase>
<info>
<keywords>
FTP
PASV
RETR
FAILURE
</keywords>
</info>
# Server-side
<reply>
<servercmd>
REPLY RETR 550 no such file!
REPLY SIZE 500 command not understood
</servercmd>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
Two FTP downloads, with failed RETR but re-used control connection
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/dir/%TESTNUMBER ftp://%HOSTIP:%FTPPORT/dir/%TESTNUMBER
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<errorcode>
78
</errorcode>
<protocol>
USER anonymous
PASS ftp@example.com
PWD
CWD dir
EPSV
TYPE I
SIZE %TESTNUMBER
RETR %TESTNUMBER
EPSV
SIZE %TESTNUMBER
RETR %TESTNUMBER
QUIT
</protocol>
</verify>
</testcase>
verify that a 550-response for a RETR returns 78 but also that the control connection is kept alive afterwards 2009-02-19 08:47:06 -05:00			`<testcase>`
			`<info>`
			`<keywords>`
			`FTP`
			`PASV`
			`RETR`
			`FAILURE`
			`</keywords>`
			`</info>`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`REPLY RETR 550 no such file!`
ftp: a 550 response to SIZE returns CURLE_REMOTE_FILE_NOT_FOUND This is primarily interesting for cases where CURLOPT_NOBODY is set as previously curl would not return an error for this case. MDTM getting 550 now also returns this error (it returned CURLE_FTP_COULDNT_RETR_FILE before) in order to unify return codes for missing files across protocols and specific FTP commands. libcurl already returns error on a 550 as a MDTM response (when CURLOPT_FILETIME is set). If CURLOPT_NOBODY is not set, an error would happen subsequently anyway since the RETR command would fail. Add test 1913 and 1914 to verify. Updated several tests accordingly due to the updated SIZE behavior. Reported-by: Tomas Berger Fixes #5953 Closes #5957 2020-09-12 12:27:08 -04:00			`REPLY SIZE 500 command not understood`
verify that a 550-response for a RETR returns 78 but also that the control connection is kept alive afterwards 2009-02-19 08:47:06 -05:00			`</servercmd>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
			`<name>`
			`Two FTP downloads, with failed RETR but re-used control connection`
			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`ftp://%HOSTIP:%FTPPORT/dir/%TESTNUMBER ftp://%HOSTIP:%FTPPORT/dir/%TESTNUMBER`
verify that a 550-response for a RETR returns 78 but also that the control connection is kept alive afterwards 2009-02-19 08:47:06 -05:00			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`78`
			`</errorcode>`
			`<protocol>`
			`USER anonymous`
			`PASS ftp@example.com`
			`PWD`
			`CWD dir`
			`EPSV`
			`TYPE I`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`SIZE %TESTNUMBER`
			`RETR %TESTNUMBER`
verify that a 550-response for a RETR returns 78 but also that the control connection is kept alive afterwards 2009-02-19 08:47:06 -05:00			`EPSV`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`SIZE %TESTNUMBER`
			`RETR %TESTNUMBER`
verify that a 550-response for a RETR returns 78 but also that the control connection is kept alive afterwards 2009-02-19 08:47:06 -05:00			`QUIT`
			`</protocol>`
			`</verify>`
			`</testcase>`