curl-curl/tests/data/test116
Viktor Szakats 6cf3d7b1b1
tests: avoid more hard-coded CRLFs in protocol sections
- fix regex to not catch CR (from CRLF), in `PORT`, `EPRT`
  commands, allowing to use `crlf="yes"` more.
- add `crlf="headers"` mode for `protocol` sections.
  To call `subnewlines()` without its force option.
  This is the mode used in `data` sections when `crlf="yes"`.
  (This confusion may be subject to a future commit.)
- subnewlines: apply CRLF to `HEAD` and `CONNECT` HTTP requests.
- subnewlines: apply CRLF to RTSP requests.
- delete remaining empty `protocol` sections.

Reducing the number of `tests/data/test*`:
- CRLF newlines from 11325 to 10295. (119984 lines total)
- files with mixed newlines from 707 to 656. (1890 files total)

Follow-up to 4d2a05d3fe #19284

Closes #19318
2025-11-01 23:52:55 +01:00

56 lines
853 B
Plaintext

<testcase>
<info>
<keywords>
FTP
EPRT
PORT
FAILURE
EPRT refused
</keywords>
</info>
# Server-side
<reply>
<servercmd>
REPLY EPRT 500 we don't like EPRT now
REPLY PORT 314 bluah you f00l!
</servercmd>
</reply>
# Client-side
<client>
<server>
ftp
</server>
# EPRT is only sent when IPv6 is enabled
<features>
IPv6
</features>
<name>
FTP download, failed PORT
</name>
<command>
ftp://%HOSTIP:%FTPPORT/%TESTNUMBER -P 1.2.3.4
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<errorcode>
30
</errorcode>
# Strip the port number but leave the rest
<strippart>
s/^(PORT \d{1,3},\d{1,3},\d{1,3},\d{1,3},)\d{1,3},\d{1,3}/$1/
s/^(EPRT \|1\|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\|)\d{1,5}\|/$1/
</strippart>
<protocol crlf="yes">
USER anonymous
PASS ftp@example.com
PWD
EPRT |1|1.2.3.4|
PORT 1,2,3,4,
QUIT
</protocol>
</verify>
</testcase>