Opened 14 years ago

Last modified 11 years ago

#992 closed Bug report

"Overwrite if newer" prevents ul retry after transfer error

Reported by: arcticwolf Owned by: Alexander Schuch
Priority: normal Component: FileZilla Client
Keywords: Cc: arcticwolf, Alexander Schuch, madpole
Component version: Operating system type:
Operating system version:

Description

Hi,

I'd like to report a bug in Filezilla 2.2.17. The
following is happening:

When you upload a number of files to an FTP server that
already exist on the server and select "overwrite if
newer" and "use this choice for all files" when
prompted, any file that does not get uploaded
completely (due to a transfer error) will not be
uploaded again.

I assume that this is due to the choice of "overwrite
if newer" - my suspicion is that when Filezilla tries
to upload the file a second time, it checks the
timestamp of the (partial) file on the server,
discovers that it's more recent than the local
timestamp, and then does not upload the file again.
This is incorrect behaviour, of course: if a file is
uploaded a second time after a transfer error, the
timestamp should not be checked again.

Change History (3)

comment:1 Changed 14 years ago by madpole

I discovered the same problem and arrived at the same
suspicion - when I had this option on I ended up with a lot
of files with 0 bytes in destination directory and with
current daytime stamp. Changing option to "overwrite"
seemed to fix this problem. I experienced this problem with
earlier versions of FileZilla, I downloaded 2.2.17 hoping
that the latest release will fix it... ;)

comment:2 Changed 11 years ago by Alexander Schuch

This bug report is quite old and FileZilla 3 got released in the mean time already. As it is a nearly complete rewrite of the FTP client, chances are that this bug has been fixed. Can you please test again with most recent FileZilla and check if the problem is still there?

comment:3 Changed 11 years ago by sf-robot

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Note: See TracTickets for help on using tickets.