curl/tests/data/test131

<testcase>
<info>
<keywords>
FTP
EPSV
LIST
netrc
</keywords>
</info>
#
# Server-side
<reply>
#
# When doing LIST, we get the default list output hard-coded in the test
# FTP server
<datacheck mode="text">
total 20
drwxr-xr-x   8 98       98           512 Oct 22 13:06 .
drwxr-xr-x   8 98       98           512 Oct 22 13:06 ..
drwxr-xr-x   2 98       98           512 May  2  1996 .NeXT
-r--r--r--   1 0        1             35 Jul 16  1996 README
lrwxrwxrwx   1 0        1              7 Dec  9  1999 bin -> usr/bin
dr-xr-xr-x   2 0        1            512 Oct  1  1997 dev
drwxrwxrwx   2 98       98           512 May 29 16:04 download.html
dr-xr-xr-x   2 0        1            512 Nov 30  1995 etc
drwxrwxrwx   2 98       1            512 Oct 30 14:33 pub
dr-xr-xr-x   5 0        1            512 Oct  1  1997 usr
</datacheck>
</reply>

#
# Client-side
<client>
<server>
ftp
</server>
 <name>
FTP (optional .netrc; user/no pass) dir list PASV
 </name>
 <command>
--netrc-optional --netrc-file log/netrc131 ftp://user2@%HOSTIP:%FTPPORT/
</command>
<file name="log/netrc131" >
# the following two lines were created while testing curl
machine %HOSTIP login user1 password passwd1
machine %HOSTIP login user2 password passwd2
</file>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
USER user2
PASS passwd2
PWD
EPSV
TYPE A
LIST
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-23 10:25:56 +08:00			`<testcase>`
keyword update 2005-04-27 17:59:47 +08:00			`<info>`
			`<keywords>`
			`FTP`
			`EPSV`
			`LIST`
Added some <keywords> sections and use some key words more consistently. 2007-10-12 09:44:22 +08:00			`netrc`
keyword update 2005-04-27 17:59:47 +08:00			`</keywords>`
			`</info>`
five new test cases for the netrc parsing 2002-05-22 06:14:08 +08:00			`#`
			`# Server-side`
David McCreedy brought line end conversions when doing FTP ASCII transfers. They are done on non-windows systems and translate CRLF to LF. 2006-04-26 15:40:37 +08:00			`<reply>`
			`#`
			`# When doing LIST, we get the default list output hard-coded in the test`
			`# FTP server`
FTP tests: enable text-mode for data and datacheck sections 2014-01-26 18:32:44 +08:00			`<datacheck mode="text">`
David McCreedy brought line end conversions when doing FTP ASCII transfers. They are done on non-windows systems and translate CRLF to LF. 2006-04-26 15:40:37 +08:00			`total 20`
			`drwxr-xr-x 8 98 98 512 Oct 22 13:06 .`
			`drwxr-xr-x 8 98 98 512 Oct 22 13:06 ..`
			`drwxr-xr-x 2 98 98 512 May 2 1996 .NeXT`
			`-r--r--r-- 1 0 1 35 Jul 16 1996 README`
			`lrwxrwxrwx 1 0 1 7 Dec 9 1999 bin -> usr/bin`
			`dr-xr-xr-x 2 0 1 512 Oct 1 1997 dev`
			`drwxrwxrwx 2 98 98 512 May 29 16:04 download.html`
			`dr-xr-xr-x 2 0 1 512 Nov 30 1995 etc`
			`drwxrwxrwx 2 98 1 512 Oct 30 14:33 pub`
			`dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr`
			`</datacheck>`
five new test cases for the netrc parsing 2002-05-22 06:14:08 +08:00			`</reply>`

			`#`
			`# Client-side`
require the netrc_debug feature the same way we now can require SSL present client-side 2003-06-13 00:38:14 +08:00			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-05-01 04:25:39 +08:00			`<server>`
			`ftp`
			`</server>`
five new test cases for the netrc parsing 2002-05-22 06:14:08 +08:00			`<name>`
			`FTP (optional .netrc; user/no pass) dir list PASV`
			`</name>`
			`<command>`
test suite: use test case specific netrc file names 2011-09-05 18:39:50 +08:00			`--netrc-optional --netrc-file log/netrc131 ftp://user2@%HOSTIP:%FTPPORT/`
five new test cases for the netrc parsing 2002-05-22 06:14:08 +08:00			`</command>`
test suite: use test case specific netrc file names 2011-09-05 18:39:50 +08:00			`<file name="log/netrc131" >`
five new test cases for the netrc parsing 2002-05-22 06:14:08 +08:00			`# the following two lines were created while testing curl`
			`machine %HOSTIP login user1 password passwd1`
			`machine %HOSTIP login user2 password passwd2`
			`</file>`
A minor "syntax error" in numerous test files corrected 2005-01-26 05:45:03 +08:00			`</client>`
five new test cases for the netrc parsing 2002-05-22 06:14:08 +08:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`USER user2`
			`PASS passwd2`
			`PWD`
			`EPSV`
			`TYPE A`
			`LIST`
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 15:08:37 +08:00			`QUIT`
five new test cases for the netrc parsing 2002-05-22 06:14:08 +08:00			`</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-23 10:25:56 +08:00			`</testcase>`