curl/tests/data/test1233, branch master cURL mirror with patches applied tests: add `connect to non-listen` keywords 2019-10-21T08:19:22+00:00 Marcel Raad Marcel.Raad@teamviewer.com 2019-10-20T18:12:52+00:00 2e4405d29c84a0803b24e14401a7a9f9d7975df3 These tests try to connect to ports nothing is listening on. Closes https://github.com/curl/curl/pull/4511 
These tests try to connect to ports nothing is listening on.

Closes https://github.com/curl/curl/pull/4511
FTP: when EPSV gets a 229 but fails to connect, retry with PASV 2013-08-06T07:57:59+00:00 Daniel Stenberg daniel@haxx.se 2013-08-05T21:49:53+00:00 7cc00d9a832c42a330888aa5c11a2abad1bd5ac0 This is a regression as this logic used to work. It isn't clear when it broke, but I'm assuming in 7.28.0 when we went all-multi internally. This likely never worked with the multi interface. As the failed connection is detected once the multi state has reached DO_MORE, the Curl_do_more() function was now expanded somewhat so that the ftp_do_more() function can request to go "back" to the previous state when it makes another attempt - using PASV. Added test case 1233 to verify this fix. It has the little issue that it assumes no service is listening/accepting connections on port 1... Reported-by: byte_bucket in the #curl IRC channel 
This is a regression as this logic used to work. It isn't clear when it
broke, but I'm assuming in 7.28.0 when we went all-multi internally.

This likely never worked with the multi interface. As the failed
connection is detected once the multi state has reached DO_MORE, the
Curl_do_more() function was now expanded somewhat so that the
ftp_do_more() function can request to go "back" to the previous state
when it makes another attempt - using PASV.

Added test case 1233 to verify this fix. It has the little issue that it
assumes no service is listening/accepting connections on port 1...

Reported-by: byte_bucket in the #curl IRC channel