Core FTP

I found a workaround, if you specify a site the transfer deals with the 0 byte transfers correctly. It must be some bug that is only there when the site is not defined.

I've noticed that the 0 byte file transfer problem only occurs when running from the command line, not when using the application interactively.

This problem seemed to go away but may have been because no 0 byte files existed in the source site...I'm not really sure. In any case, it is happening again. I'm not sure what log you are referring to, the output log just lists the files that are being transferred and it clearly points to the issue...

When using CoreFTP Lite in command line mode with recursive directory downloads, the process gets hung on 0 byte files. We are using SSL, using command -OA -s -hide and it just hangs on a 0 byte file.

The 0 byte file is in a subdirectory of the top-level of the site.

Any suggestions?

Rob