Re: [twsocket] FTP Client - Large files
> Filezilla seems to handle with a no response timeout, followed by a > query, some times even a reconnect, to check if the file is > effectively there, and with the correct size. Similar features are the benefit of using the TMagFtp high level component. It also checks the correct sized file has been uploaded, will do a CRC32 or MD5 check to ensure it's not been corrupted, and will repeat the upload if necessary. But I'm not aware TMagFtp specifically handles a missing response, unless by accident! Most servers will timeout the control connection anyway once activity ceases that could cause TMagFtp to close everything down. Without having seen any proper FTP logs for this bad server, this is all conjecture. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] FTP Client - Large files
On 28-11-2012 08:51, Graham Powell wrote: 1: Can the FTP client be modified to generate the ftpPutAsync event on something else as well as the Transfer Complete. Wireshark always shows some message at the end that contains FIN ACK. Sometimes, when I'm updating my web site using Filezilla, and specially with large files, I think I also experience this lack of confirmation of transfer complete, that Filezilla seems to handle with a no response timeout, followed by a query, some times even a reconnect, to check if the file is effectively there, and with the correct size. I'm not used to the FTP protocol, so never gave attention to the Filezilla activity log, to see what's exactly happening, but that's the idea I get. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] FTP Client - Large files
- Original Message - From: "Angus Robertson - Magenta Systems Ltd" To: Sent: Wednesday, November 28, 2012 11:36 AM Subject: Re: [twsocket] FTP Client - Large files >> It would appear that this FTP site does not send a "FTP 226 Transfer >> Complete" for large files. > > So it's a faulty FTP server, not a problem with the FTP client. Or only that server is behind a router or it is the slowest. I still think it's likely a faulty router that times out the control connection, hence the "FTP 226 Transfer Complete" response is very likely sent however dropped by the router, so not logged in Wireshark. -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] FTP Client - Large files
> It would appear that this FTP site does not send a "FTP 226 Transfer > Complete" for large files. So it's a faulty FTP server, not a problem with the FTP client. I've already asked what make of FTP software and am waiting for your response. You have not posted any FTP logs (the full FTP session) which might identify it. > is there something special about "putAsync" th I explained all that yesterday. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] FTP Client - Large files
I am trying to see as much information as possible to get an idea of where the problem lies. It would appear that this FTP site does not send a "FTP 226 Transfer Complete" for large files. So in this case you cannot use the ftpPutAsync event to know when the upload has finished. I have used Wireshark to monitor what is sent when you just drag & drop the file to the FTP server using Windows Explorer. Again there is no Transfer Complete, but everything works fine. 1: Can the FTP client be modified to generate the ftpPutAsync event on something else as well as the Transfer Complete. Wireshark always shows some message at the end that contains FIN ACK. 2: Is there something special about "putAsync" that makes it different to just "Put" with regard to generating the final event. Graham -Original Message- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of Arno Garrels Sent: 27 November 2012 19:22 To: ICS support mailing Subject: Re: [twsocket] FTP Client - Large files Angus Robertson - Magenta Systems Ltd wrote: > Not sure why you using Wireshark, the FTP component has all the events > you need to log the FTP protocol, even without the logger component. I think he uses Wireshark because, and that makes sense, he wants to know whether or not the server response to the PUT request is actually received. >From how I read OP's messages the response to the PUT request is sometimes and sometimes not included in the Wireshark logs, which is at least strange. -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be