curl/tests/data/test228

<testcase>
<info>
<keywords>
FTP
ACCT
compressed
</keywords>
</info>
# Server-side
<reply>
<data>
data
    to
      see
that FTP
works
  so does it?
</data>
<servercmd>
REPLY PASS 332 please provide account name
REPLY ACCT 230 thank you
</servercmd>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP RETR with ACCT
 </name>
 <command>
ftp://%HOSTIP:%FTPPORT/228 --ftp-account "one count"
</command>
</client>


# Verify data after the test has been "shot"
<verify>
<protocol>
USER anonymous
PASS ftp@example.com
ACCT one count
PWD
EPSV
TYPE I
SIZE 228
RETR 228
QUIT
</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>`
added keywords 2005-05-21 18:38:19 -04:00			`<info>`
			`<keywords>`
			`FTP`
			`ACCT`
			`compressed`
			`</keywords>`
			`</info>`
Ian Ford asked about support for the FTP command ACCT, and I discovered it is present in RFC959... so now (lib)curl supports it as well. --ftp-account and CURLOPT_FTP_ACCOUNT set the account string. (The server may ask for an account string after PASS have been sent away. The client responds with "ACCT [account string]".) Added test case 228 and 229 to verify the functionality. Updated the test FTP server to support ACCT somewhat. 2005-01-25 17:13:12 -05:00			`# Server-side`
			`<reply>`
			`<data>`
			`data`
			`to`
			`see`
			`that FTP`
			`works`
			`so does it?`
			`</data>`
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			`<servercmd>`
			`REPLY PASS 332 please provide account name`
			`REPLY ACCT 230 thank you`
			`</servercmd>`
Ian Ford asked about support for the FTP command ACCT, and I discovered it is present in RFC959... so now (lib)curl supports it as well. --ftp-account and CURLOPT_FTP_ACCOUNT set the account string. (The server may ask for an account string after PASS have been sent away. The client responds with "ACCT [account string]".) Added test case 228 and 229 to verify the functionality. Updated the test FTP server to support ACCT somewhat. 2005-01-25 17:13:12 -05:00			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`ftp`
			`</server>`
			`<name>`
			`FTP RETR with ACCT`
			`</name>`
			`<command>`
			`ftp://%HOSTIP:%FTPPORT/228 --ftp-account "one count"`
			`</command>`
			`</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`
Ian Ford asked about support for the FTP command ACCT, and I discovered it is present in RFC959... so now (lib)curl supports it as well. --ftp-account and CURLOPT_FTP_ACCOUNT set the account string. (The server may ask for an account string after PASS have been sent away. The client responds with "ACCT [account string]".) Added test case 228 and 229 to verify the functionality. Updated the test FTP server to support ACCT somewhat. 2005-01-25 17:13:12 -05:00			`ACCT one count`
			`PWD`
			`EPSV`
			`TYPE I`
			`SIZE 228`
			`RETR 228`
			`QUIT`
			`</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>`