Running coreFTP on :
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~2400 Mhz
FTP CoreFTP - Version 1.3, build 1403 (Free Version)
Connecting to :
OS Name FreeBSD
Version 4.4 UNIX O/S
Processor Intel Pentium III CPU
FTP Proftpd - Version 1.2.10
When I am pulling large amounts of files down, just like lostangel, I am getting a hang on zero byte files.
The current work around:
I 'Reset Status' on the hung file, the remaining files contiune (with the following file showing as aborted). When the original set of transfers are completed, I must reset all the aborted and start them, everything completes as normal.
This is quite a hassel for the particular server I am working with at the moment as they are using session files that do not get deleted (yes, I know this is bad practice...) that are 0 byte files. There are as many as 2,500 of these for each vitrual host.
My question would be, is there a way that I could bypass these files all together since there is no need for me to keep them? I am strictly doing an archive of these servers.
I am seriously considering buying the paid version of this software as it has a lot of features I like, but I can't see doing it with this issue in place.
I am in fact using SSL (sorry for the earlier omission). Auth TLS, SSL Listings and SSL Transfers: Open SSL.
Some servers I deal with require this type of connection, others do not. I have just been using this type of connection on all of them.
Is there a resolution to the SSL based transfers and 0 byte files, or this just a known issue?
I have not given the ANSI version a try yet, but based on the SSL, will this make a difference?
Are there some docs or previous forum comments on this that I missed?
BTW, after looking at the log files, there is no mention of any problems when downloading these files. The log for them looks exactly as any other file.
SAMPLE CORE_FTP.LOG (paths edited)
...
20041229 10:05:51 Download C:\...\Session_files\38d655c119d44fd8.dat from /.../Session_files/38d655c119d44fd8.dat
20041229 10:05:54 Download C:\...\Session_files\38d755c119e45fd8.dat from /.../Session_files/38d755c119e45fd8.dat
...
The 38d655c119d44fd8.dat is a 0 byte file. The 38d755c119e45fd8.dat is a 28 byte file. No difference that I can see between the two. Is there by chance another log file that I am to look at? This is from the log file in the associated directory of the transfers.
After trying the some of the sites without the SSL encryption, everything works as it should (I had forgotten how much overhead encryption takes...).
I am probably going to go ahead and buy the pro version, but I would like to know if you have plans for an SSL fix, or if it is even possible.
Does this happen only on the first file that has zero bytes or after several successive transfers of zero byte files?
Well, I wish I could give you a reproducable scenario, but it is not always the same.
Sometimes it hangs on the first 0 byte file, and all successive 0 byte files go through as successful (until the next non-zero byte file followed by a 0 byte file), other times it hangs on each one.
In any case, if a 0 byte file is preceeded with a non-zero byte file, it always hangs on that 0 byte file until I reset it.