aboutsummaryrefslogtreecommitdiff
path: root/tests/data
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2006-01-24 14:40:43 +0000
committerDaniel Stenberg <daniel@haxx.se>2006-01-24 14:40:43 +0000
commit67bf4f28ffcd7102602a83343da8df8058f9af4f (patch)
treecb528243df2039d951c85f9744b08413c58d581a /tests/data
parent803582f8ac264e5932d364208cbf475c84a4964f (diff)
Michal Marek provided a patch for FTP that makes libcurl continue to try PASV
even after EPSV returned a positive response code, if libcurl failed to connect to the port number the EPSV response said. Obviously some people are going through protocol-sensitive firewalls (or similar) that don't understand EPSV and then they don't allow the second connection unless PASV was used. This also called for a minor fix of test case 238.
Diffstat (limited to 'tests/data')
-rw-r--r--tests/data/test23812
1 files changed, 9 insertions, 3 deletions
diff --git a/tests/data/test238 b/tests/data/test238
index c314f6b7c..8e23b4fb0 100644
--- a/tests/data/test238
+++ b/tests/data/test238
@@ -8,26 +8,32 @@
ftp
</server>
<name>
-FTP getting bad port in 229-response to EPSV
+FTP getting bad port in response to EPSV and in response to PASV
</name>
<command>
ftp://%HOSTIP:%FTPPORT/238
</command>
<file name="log/ftpserver.cmd">
REPLY EPSV 229 Entering Passiv Mode (|||1000000|)
+REPLY PASV 227 Entering Passiv Mode (1216,256,2,127,127,127)
</file>
</client>
# Verify data after the test has been "shot"
<verify>
-# 7 => CURLE_COULDNT_CONNECT
+# 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?
+# 7= CURLE_COULDNT_CONNECT
<errorcode>
-7
+7, 15
</errorcode>
<protocol>
USER anonymous
PASS curl_by_daniel@haxx.se
PWD
EPSV
+PASV
</protocol>
</verify>