diff options
author | Jay Satiro <raysatiro@yahoo.com> | 2016-08-22 15:37:03 -0400 |
---|---|---|
committer | Jay Satiro <raysatiro@yahoo.com> | 2016-09-07 21:24:27 -0400 |
commit | af2d679e1414369f23a2d37a113634b0ac7f38b0 (patch) | |
tree | 0d6263b9a37817fbe2c7c1b52b3118b8a2c83ef6 /tests/data | |
parent | add8ee7d57bf9d61a586126e1182e7eb356834fe (diff) |
errors: new alias CURLE_WEIRD_SERVER_REPLY (8)
Since we're using CURLE_FTP_WEIRD_SERVER_REPLY in imap, pop3 and smtp as
more of a generic "failed to parse" introduce an alias without FTP in
the name.
Closes https://github.com/curl/curl/pull/975
Diffstat (limited to 'tests/data')
-rw-r--r-- | tests/data/test2045 | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/data/test2045 b/tests/data/test2045 index 3190f803b..15647d3e7 100644 --- a/tests/data/test2045 +++ b/tests/data/test2045 @@ -19,7 +19,7 @@ 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_FTP_WEIRD_SERVER_REPLY so we test for that return code. +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 @@ -46,7 +46,7 @@ Set the default protocol to ftp for a schemeless URL # # Verify data after the test has been "shot" <verify> -# CURLE_FTP_WEIRD_SERVER_REPLY is error code 8 +# CURLE_WEIRD_SERVER_REPLY is error code 8 <errorcode> 8 </errorcode> |