curl/tests/data/test136

# Server-side
<reply>
<data>
0123456789abcdef
</data>
</reply>

# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP with user and no password
 </name>
 <command>
-u user: ftp://%HOSTIP:%FTPPORT/136
</command>
</test>

# Verify data after the test has been "shot"
<verify>
<protocol>
USER user
PASS 
PWD
EPSV
TYPE I
SIZE 136
RETR 136
QUIT
</protocol>
</verify>
verify -u username: with ftp to use a blank password 2003-01-09 11:47:55 -05:00			`# Server-side`
			`<reply>`
			`<data>`
			`0123456789abcdef`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`ftp`
			`</server>`
verify -u username: with ftp to use a blank password 2003-01-09 11:47:55 -05:00			`<name>`
			`FTP with user and no password`
			`</name>`
			`<command>`
			`-u user: ftp://%HOSTIP:%FTPPORT/136`
			`</command>`
			`</test>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`USER user`
			`PASS`
			`PWD`
			`EPSV`
			`TYPE I`
			`SIZE 136`
			`RETR 136`
Joe Halpin made the FTP code send 'QUIT' on the control connection before it disconnects the TCP connection, like a good ftp client should! 2004-02-27 02:08:37 -05:00			`QUIT`
verify -u username: with ftp to use a blank password 2003-01-09 11:47:55 -05:00			`</protocol>`
			`</verify>`