Cyberduck Mountain Duck CLI

#2687 closed defect (wontfix)

Transfer is complete but it says it failed!

Reported by: darmok Owned by: dkocher
Priority: normal Milestone:
Component: ftp Version: 3.0.2
Severity: normal Keywords:
Cc: dantearmok@… Architecture:

Description (last modified by dkocher)

Using Cyberduck 3.0.3 (4205), OS X 10.4.11, Java 1.5.0_16

I downloaded a large file, > 1 GB, from an ftp server. The transfer failed repeatedly but the automatic retries kept things going.

Ultimately, it growled twice:

Oct 23, 2008 10:20:19 AM Cyberduck: Download complete (testfile.mpx ) - Priority 0[[BR]]
Oct 23, 2008 10:20:20 AM Cyberduck: Connection failed ( - Priority 0

... cosmetic bug: the extra space after the file name, before the close-paren.

When I brought Cyberduck forward, the Transfers window had a Failures (probably should be singular) sheet showing that said:

FTP Error: Download failed.
(the file's path)
ransfer complete.

... cosmetic bug: It says "ransfer" - with a missing T.

The transcript below that says:

26 Transfer complete.
221 Goodbye.

I checked the file - the download *is* complete; its length is exactly right. Not sure why Cyberduck thought the download failed...

See attached screen snapshot of the Failure sheet.

Attachments (1)

Failed but complete.jpg (46.9 KB) - added by darmok on Oct 23, 2008 at 3:50:02 PM.

Download all attachments as: .zip

Change History (3)

Changed on Oct 23, 2008 at 3:50:02 PM by darmok

comment:1 Changed on Oct 30, 2008 at 7:38:22 PM by dkocher

  • Component changed from core to ftp
  • Description modified (diff)

comment:2 Changed on Oct 30, 2008 at 7:43:19 PM by dkocher

  • Resolution set to wontfix
  • Status changed from new to closed

The status response code from the server must always have a length of three digits. E.g. for a completed transfer, it is expected to be one of 225, 226 or 250. Please report to the server vendor.

Note: See TracTickets for help on using tickets.