curl/tests/data/test236

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

# Server-side
<reply>
<servercmd>
REPLY SIZE 550 access to this file is very much denied
REPLY APPE 550 I said: access to this file is very much denied
REPLY STOR 550 I said: access to this file is very much denied
</servercmd>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP resume upload but denied access to remote file
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/236 -T log/file236.txt -C -
</command>
<file name="log/file236.txt">
Test data
</file>
</client>

# Verify data after the test has been "shot"
<verify>

<protocol>
USER anonymous
PASS ftp@example.com
PWD
EPSV
TYPE I
SIZE 236
STOR 236
QUIT
</protocol>

#  (25) Failed FTP upload: 550
<errorcode>
25
</errorcode>
</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>`
Add FTP keywords for a couple of currently keyword-less FTP tests 2012-11-16 06:42:51 -05:00			`<info>`
			`<keywords>`
			`FTP`
			`</keywords>`
			`</info>`
Various test file cleanups, including using <servercmd> instead of writing directly to ftpserver.cmd and removing unneeded empty sections. 2007-04-18 16:22:01 -04:00
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`REPLY SIZE 550 access to this file is very much denied`
			`REPLY APPE 550 I said: access to this file is very much denied`
			`REPLY STOR 550 I said: access to this file is very much denied`
			`</servercmd>`
			`</reply>`

test 236: FTP resume upload but denied access to remote file 2005-03-07 03:29:28 -05:00			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
			`<name>`
			`FTP resume upload but denied access to remote file`
			`</name>`
			`<command>`
Various test file cleanups, including using <servercmd> instead of writing directly to ftpserver.cmd and removing unneeded empty sections. 2007-04-18 16:22:01 -04:00			`ftp://%HOSTIP:%FTPPORT/236 -T log/file236.txt -C -`
test 236: FTP resume upload but denied access to remote file 2005-03-07 03:29:28 -05:00			`</command>`
Various test file cleanups, including using <servercmd> instead of writing directly to ftpserver.cmd and removing unneeded empty sections. 2007-04-18 16:22:01 -04:00			`<file name="log/file236.txt">`
			`Test data`
test 236: FTP resume upload but denied access to remote file 2005-03-07 03:29:28 -05:00			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`

			`<protocol>`
			`USER anonymous`
ftp@example.com is now the new anonymous FTP password. I opted for 'ftp' on the left side of @ to make it short(er). 2007-02-13 17:50:16 -05:00			`PASS ftp@example.com`
test 236: FTP resume upload but denied access to remote file 2005-03-07 03:29:28 -05:00			`PWD`
			`EPSV`
			`TYPE I`
			`SIZE 236`
			`STOR 236`
Added test case 531 in an attempt to repeat bug report #1561470 (http://curl.haxx.se/bug/view.cgi?id=1561470) that is said to crash when an FTP upload fails with the multi interface. It did not, but I made a failed upload still assume the control connection to be fine. 2006-09-21 16:52:20 -04:00			`QUIT`
test 236: FTP resume upload but denied access to remote file 2005-03-07 03:29:28 -05:00			`</protocol>`

			`# (25) Failed FTP upload: 550`
			`<errorcode>`
			`25`
			`</errorcode>`
			`</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>`