curl/tests/data/test1913

<testcase>
<info>
<keywords>
FTP
CURLOPT_NOBODY
</keywords>
</info>

# Server-side
<reply>
<servercmd>
REPLY SIZE 550 no such file
</servercmd>
</reply>

# Client-side
<client>
<server>
ftp
</server>

# require debug so that alt-svc can work over plain old HTTP
<name>
FTP with NOBODY set, getting a missing file
</name>
<tool>
lib1913
</tool>

<command>
ftp://%HOSTIP:%FTPPORT/not-there/1913
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<errorcode>
78
</errorcode>
</verify>
</testcase>
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			`<testcase>`
			`<info>`
			`<keywords>`
			`FTP`
			`CURLOPT_NOBODY`
			`</keywords>`
			`</info>`

			`# Server-side`
			`<reply>`
			`<servercmd>`
			`REPLY SIZE 550 no such file`
			`</servercmd>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`

			`# require debug so that alt-svc can work over plain old HTTP`
			`<name>`
			`FTP with NOBODY set, getting a missing file`
			`</name>`
			`<tool>`
			`lib1913`
			`</tool>`

			`<command>`
			`ftp://%HOSTIP:%FTPPORT/not-there/1913`
			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<errorcode>`
			`78`
			`</errorcode>`
			`</verify>`
			`</testcase>`