mirror of
https://github.com/curl/curl.git
synced 2026-04-15 00:41:41 +03:00
3fd80c7b59
The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028
60 lines
1 KiB
Text
60 lines
1 KiB
Text
<testcase>
|
|
<info>
|
|
<keywords>
|
|
FTP
|
|
PORT
|
|
RETR
|
|
NODATACONN
|
|
timeout
|
|
FAILURE
|
|
</keywords>
|
|
</info>
|
|
# Server-side
|
|
<reply>
|
|
<data nocheck="yes">
|
|
some bytes
|
|
</data>
|
|
<servercmd>
|
|
NODATACONN
|
|
</servercmd>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
ftp
|
|
</server>
|
|
<name>
|
|
FTP PORT download, no data conn and no positive preliminary reply
|
|
</name>
|
|
<command>
|
|
--max-time %FTPTIME2 ftp://%HOSTIP:%FTPPORT/%TESTNUMBER -P -
|
|
</command>
|
|
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<strippart>
|
|
s/^EPRT \|1\|(.*)/EPRT \|1\|/
|
|
</strippart>
|
|
|
|
# The protocol part does not include QUIT simply because the error is
|
|
# CURLE_OPERATION_TIMEDOUT (28) which is a generic timeout error without
|
|
# specifically saying for which connection it concerns, and for timeouts libcurl
|
|
# marks the control channel as "invalid". As this test case times out for the
|
|
# data connection it could still use the control channel.
|
|
<protocol>
|
|
USER anonymous
|
|
PASS ftp@example.com
|
|
PWD
|
|
EPRT |1|
|
|
TYPE I
|
|
SIZE %TESTNUMBER
|
|
RETR %TESTNUMBER
|
|
</protocol>
|
|
<errorcode>
|
|
28
|
|
</errorcode>
|
|
</verify>
|
|
</testcase>
|