mirror of
https://github.com/curl/curl.git
synced 2024-11-21 01:16:58 +08:00
67bf4f28ff
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.
40 lines
797 B
Plaintext
40 lines
797 B
Plaintext
# Server-side
|
|
<reply>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
ftp
|
|
</server>
|
|
<name>
|
|
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>
|
|
# 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, 15
|
|
</errorcode>
|
|
<protocol>
|
|
USER anonymous
|
|
PASS curl_by_daniel@haxx.se
|
|
PWD
|
|
EPSV
|
|
PASV
|
|
</protocol>
|
|
</verify>
|