The exception is the ABOR command which aborts any previous command, skipping its reply. Modern clients if they wish to abort should simply close the connection.Įxplanation for the ABOR issue: In FTP there must be exactly one reply for every command. The semantics of the ABOR command are ill-defined by the FTP specifications, it should not be used by modern clients. The client always sends _both_ PASV and PORT, first switching to passive mode only to immediately switch back to active mode. I already posted a ticket to FileZilla tem: From server side - there is more chance for interrupted transfer, if try to download a folder with a lot of small files (real example - saved webpages with all their resources/images/scripts)Ĭhristian, if you will have some time - can you please review this issue ? If needed - I can make some test area on my own filezilla-based FTP server. What I know - it not depends on connection way (SSL or normal, passive or not), but depends on client side - there is more prolems when client is an old slow PC and/or slow internet connection.

Also I'm not even sure that problem is on TC side (but official FileZilla client have no problems with same server).

I'm not sure what is source of a problem, filezilla server log not helpful in this case too.

It loks like appeared from some FileZilla server update near 2 years ago. There is a problem that present for a long time - TC have bad compatibility with current FileZilla server - it may sometimes show empty folders that are full of files or drop filetransfer after random file.

Cost of filezilla pro server and client