aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDan Fandrich <dan@coneharvesters.com>2005-03-17 20:50:17 +0000
committerDan Fandrich <dan@coneharvesters.com>2005-03-17 20:50:17 +0000
commit5b3730feae0f312a3c4fee688a9b6862e0df45ab (patch)
tree0c6681cb28419896ef933c06cf727c54f7b54011
parent38f797ccd644b119d22e3718ade740f5095cc880 (diff)
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).
-rw-r--r--tests/data/test2377
1 files changed, 5 insertions, 2 deletions
diff --git a/tests/data/test237 b/tests/data/test237
index be7dfd58e..c276da917 100644
--- a/tests/data/test237
+++ b/tests/data/test237
@@ -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?