From: Viktor Szakats Date: Wed, 12 Nov 2025 16:41:54 +0000 (+0100) Subject: test2045: replace HTML multi-line comment markup with `#` comments X-Git-Tag: rc-8_18_0-1~328 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8a19bf862a82bf4e8ef83b9754b071dca5494c0b;p=thirdparty%2Fcurl.git test2045: replace HTML multi-line comment markup with `#` comments As used everywhere else in tests/data. To play nice with XML. Follow-up to 9756d1da7637d1913b7ca2b589e4635f32ed3e00 Closes #19498 --- diff --git a/tests/data/test2045 b/tests/data/test2045 index 41b31e5409..241d9fc14f 100644 --- a/tests/data/test2045 +++ b/tests/data/test2045 @@ -10,17 +10,15 @@ FTP # # Server-side - +# 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. REPLY welcome HTTP/1.1 200 OK\r\nContent-Length: 21\r\n\r\n500 Weird FTP Reply