moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-14 05:25:06 -05:00
Code Issues Releases Wiki Activity
3a283968f4
curl/tests/data/test237

49 lines
1015 B
Plaintext
Raw Normal View History

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>
test EPSV and PASV response handling when they get well-formated data back but using illegal values
2005-03-15 07:33:08 -05:00
# Server-side
<reply>
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 PASV 227 Entering Passiv Mode (1216,256,2,127,127,127)
</servercmd>
test EPSV and PASV response handling when they get well-formated data back but using illegal values
2005-03-15 07:33:08 -05:00
</reply>
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP getting bad host in 227-response to PASV
</name>
<command>
ftp://%HOSTIP:%FTPPORT/237 --disable-epsv
</command>
</client>
# Verify data after the test has been "shot"
Change the bogus address used in test237 to be more reliable when run on a host with a buggy resolver that strips all but the bottom 8 bits of each octet. The resolved address in this case (192.0.2.127) is guaranteed never to belong to a real host (see RFC3330).
2005-03-17 15:50:17 -05:00
# The bogus address used here is chosen specifically so that when processed on
# certain hosts with buggy resolver code, the resulting address (192.0.2.127)
# is from an address block that is guaranteed never to be assigned (RFC3330).
test EPSV and PASV response handling when they get well-formated data back but using illegal values
2005-03-15 07:33:08 -05:00
<verify>
Change the bogus address used in test237 to be more reliable when run on a host with a buggy resolver that strips all but the bottom 8 bits of each octet. The resolved address in this case (192.0.2.127) is guaranteed never to belong to a real host (see RFC3330).
2005-03-17 15:50:17 -05:00
# curl: (15) Can't resolve new host 1216.256.2.127:32639
test EPSV and PASV response handling when they get well-formated data back but using illegal values
2005-03-15 07:33:08 -05:00
# 15 => CURLE_FTP_CANT_GET_HOST
support multiple error codes for a test case since some things just vary between platforms
2005-03-17 03:17:48 -05:00
# some systems just don't fail on the illegal host name/address but instead
# moves on and attempt to connect to... yes, to what?
# 7= CURLE_COULDNT_CONNECT
test EPSV and PASV response handling when they get well-formated data back but using illegal values
2005-03-15 07:33:08 -05:00
<errorcode>
support multiple error codes for a test case since some things just vary between platforms
2005-03-17 03:17:48 -05:00
15, 7
test EPSV and PASV response handling when they get well-formated data back but using illegal values
2005-03-15 07:33:08 -05:00
</errorcode>
<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 EPSV and PASV response handling when they get well-formated data back but using illegal values
2005-03-15 07:33:08 -05:00
PWD
PASV
</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. & => &amp; ). 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>
Reference in New Issue Copy Permalink