Opened 8 years ago

Last modified 8 years ago

#7436 new Bug report

Failed recursive directory upload

Reported by: moire Owned by:
Priority: high Component: FileZilla Client
Keywords: ssh, recursive, upload, ssh_fxp_status, ssh_fxp_realpath Cc:
Component version: Operating system type: Windows
Operating system version: Windows XP

Description

case: filezilla 3.5, ssh connection, uploading whole directory

It seems that filezilla improperly handles the response to the SSH_FXP_REALPATH command. According to the ssh drafts the server can reply with the the SSH_FXP_STATUS upon failure (Specified file path is invalid. reason=2; File not found reason=2) and from then on it is client responsibility to act upon those responses.

Server side responses:

Sending SSH_FXP_STATUS: : /00149642: Specified file path is invalid. reason=2

Sending SSH_FXP_STATUS: : File not found reason=2

Usually when a directory does not exist on the remote server, the client will receive such error message and then should issue the make directory.

Attached is the filezilla log in debug mode.

Attachments (1)

filezilla.log (37.7 KB) - added by moire 8 years ago.
filezilla debug log during failed directory upload

Download all attachments as: .zip

Change History (2)

Changed 8 years ago by moire

Attachment: filezilla.log added

filezilla debug log during failed directory upload

comment:1 Changed 8 years ago by Scott

Priority: normalhigh

I am also experiencing a similar issue with Maverick SSHD version 1.4.32 - bug# 7757

Note: See TracTickets for help on using tickets.