Looking at the log, I note the aborted transfer occurs within the first connection that is not immediately available ("Data conn was not available immediately").

I tried to simulate, forcing this condition, without success.

Since this is said to use the multi interface, the control is returned to the caller after this temporary "failure", expecting another perform call to recheck the connection later.

I then suspect there is some interaction between the caller and the non-terminated transfer: something like curl_easy_cleanup() before transfer end.

Would it be possible to see the code ?

---
** [bugs:#1436] ftp upload fails: "server did not report OK, got 150" when server replied 226**
**Status:** open-confirmed
**Labels:** libcurl ftp 
**Created:** Wed Oct 22, 2014 10:15 AM UTC by Ognyan Tonchev
**Last Updated:** Wed Oct 22, 2014 12:40 PM UTC
**Owner:** Daniel Stenberg
server did not report OK, got 150
Sending error: failed to transfer data: Transferred a partial file
I am triggering this error when uploading files to a FTP server(filezilla in Windows in this case) and when poll(in select.c) returns 0 and "Data conn was not available immediately" happens.
The problem is clearly visible in the attached Wireshark log. The TCP connection for the data transfer is established but then libcurl sends RESET and another try to send the same file is made. This second try results in success but libcurl insists on getting 150 when it gets 226.
I suspect that the 150 result is a left-over from the previous upload. Basically a return code that was not properly cleared.
Attaching both, a wireshark capture log plus log messages from libcurl when the problem occurs.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.