8a19bf862a
Viktor Szakats
2025-11-12
Subject
test2045: replace HTML multi-line comment markup with `#` comments
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
tests/data/test2045+9 -11
| @@ -10,17 +10,15 @@ FTP | |
| # | |
| # 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. |
| - | --> |
| + | # 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> | |