bug in resuming files?
 

I'm using the latest version (build 869) and I've noticed a bug in resuming. I have it set to use APPE to resume uploads, and whenever a file is resumed, it apparently fails CRC checking, the rar file is corrupt. It hasn't been a random thing either, it seems everytime a file is resumed, it fails the SFV check.

*BUMP*

41 views of this thread and no one has anything to say? has no one had this problem?

if i'm not mistaken appe should really be used only with warftpd servers cuase they are messed up in this area..i'm not sure how it would affect other ftpd, personally i never use it.

also make sure you are transfering files as TYPE I and not TYPE A.

LoKi, you're most likely trying to resume a file on a glftpd server or another server that supports 'on-the-fly' CRC32 generation. The CRC32 is only calculated over the 'uploaded' data (only the resumed part!), therefore you're getting an SFV error...

no its not that the script says it's bad.. When I fxp a file, and it it resumed, for whatever reason, when the file finished (15,000,000) it's corrupt. I've tried a standalone SFV checker, as well as tried to extract it with winrar, and both say it's corrupt. I have tried turning off APPE to see if it fixes the problem, will keep ya's posted on results. Also, I have made sure that the files aren't being transfered as ASCII (TYPE A), that was one of the first things I looked at.

Any reason why you're not using REST? does it mess up using REST too?

I was originally using APPE due to an issue with one of the sites I was using, but since the issue was resolved, it just became second nature really. I have tried turning it off, and will keep you apprised after a few trials over various sites.

well good news.. it doesn't appear to cause corrupt files when using REST instead of APPE. I will continue with APPE turned off, but maybe you might look into why APPE can cause invalid CRC's on files, incase someone else might need it to be turned on.

I'm glad to see REST is working.

APPE and REST worked fine on all of my ftp servers, I suspected the problem was caused by the ftp server.

From my point of view there isn't anything more I can do.