Failed transfers are most probably not related to the QUIT issue. To
debug logs, maybe packet dumps.
data transfers.
Post by T***@bertelsmann.deOK, thank you.
Just for your information: Weâre using a managed file transfer (MFT)
product called Ayway Synchrony Gateway as a multi-protocol service
(supports FTP, FTPS, SFTP, HTTPS, and so on). And this solution checks for
complete transfers, which means it checks the data flow, if a transfer is
correct or not. And if itâs not correct we will get an interrupted
transfer. Most of our transfers between Synchrony Gateway <-> lftp works
fine, but every now and then weâll get failed transfers. So this bug is
quite important for us, but I wonder why most of the transfers are working
fine, if this bug was already in lftp for years. Any idea?
*Sent:* Tuesday, October 21, 2014 1:03 PM
*To:* MÃŒtze, Tilo, NMD-C4.2
*Subject:* Re: [lftp] Question regarding fix in 4.6.0
I mean: it is not fixed in 4.5.6.
No, it isn't. I have decided that the change is too significant to include
in a maintenance release. Use 4.6. And I don't consider it a serious bug -
it was there for years and nobody complained.
Hi Alexander,
weâve seen that in 4.6.0 a bug âftp: wait for QUIT reply before closing
control socket.â was fixed. Can you please tell us, if this fixed bug is
present in release 4.5.6 ?
Thanks and regards,
Tilo
_______________________________________________
lftp mailing list
http://univ.uniyar.ac.ru/mailman/listinfo/lftp