mirror of
https://github.com/curl/curl.git
synced 2026-04-11 12:01:42 +08:00
b5ea0736bb
To formalize they are now XML-compliant (with some asterisks.) Also to help syntax highlighters work on them to make their content more readable. Also: - Delete empty comment decorations. - GHA/checksrc: simplify XML check. - runtests: fail to load test data with XML prolog missing. Follow-up tobfe6eb1c06#19927 Follow-up to87ba80a6dfCloses #19946
47 lines
1.2 KiB
XML
47 lines
1.2 KiB
XML
<?xml version="1.0" encoding="US-ASCII"?>
|
|
<testcase>
|
|
<info>
|
|
<keywords>
|
|
FTP
|
|
--proto-default
|
|
</keywords>
|
|
</info>
|
|
|
|
# Server-side
|
|
<reply>
|
|
# The purpose of this test is to make sure the --proto-default option works
|
|
# properly. We specify a default protocol of FTP and if the option works properly
|
|
# curl will use the FTP protocol. If the option is broken however curl will use
|
|
# the HTTP protocol.
|
|
# In the broken scenario curl would use HTTP to talk to our FTP server. We handle
|
|
# that by replying with something that both protocols can understand. Our FTP
|
|
# server allows a custom welcome message, so we use that feature to make an HTTP
|
|
# reply that contains an FTP reply (think polyglot). In the case of FTP we expect
|
|
# curl will return CURLE_WEIRD_SERVER_REPLY so we test for that return code.
|
|
<servercmd>
|
|
REPLY welcome HTTP/1.1 200 OK\r\nContent-Length: 21\r\n\r\n500 Weird FTP Reply
|
|
</servercmd>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
ftp
|
|
</server>
|
|
<name>
|
|
Set the default protocol to ftp for a schemeless URL
|
|
</name>
|
|
<command>
|
|
-H "User-Agent:" -H "Host:" -H "Accept:" --proto-default ftp %HOSTIP:%FTPPORT
|
|
</command>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
# CURLE_WEIRD_SERVER_REPLY is error code 8
|
|
<errorcode>
|
|
8
|
|
</errorcode>
|
|
</verify>
|
|
</testcase>
|