moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-21 23:58:49 -05:00
Code Issues Releases Wiki Activity

Change the bogus address used in test237 to be more reliable when run

Browse Source 
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).
This commit is contained in:
Dan Fandrich 2005-03-17 20:50:17 +00:00
parent 38f797ccd6
commit 5b3730feae
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
tests/data/test237
View File

@ -14,13 +14,16 @@ FTP getting bad host in 227-response to PASV
ftp://%HOSTIP:%FTPPORT/237 --disable-epsv
</command>
<file name="log/ftpserver.cmd">
REPLY PASV 227 Entering Passiv Mode (1218,91,256,127,127,127)
REPLY PASV 227 Entering Passiv Mode (1216,256,2,127,127,127)
</file>
</client>
# Verify data after the test has been "shot"
# 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).
<verify>
# curl: (15) Can't resolve new host 1218.91.256.127:32639
# curl: (15) Can't resolve new host 1216.256.2.127:32639
# 15 => CURLE_FTP_CANT_GET_HOST
# some systems just don't fail on the illegal host name/address but instead
# moves on and attempt to connect to... yes, to what?