Opened 12 years ago
Last modified 12 years ago
#7436 new Bug report
Failed recursive directory upload
|Reported by:||moire||Owned by:|
|Keywords:||ssh, recursive, upload, ssh_fxp_status, ssh_fxp_realpath||Cc:|
|Component version:||Operating system type:||Windows|
|Operating system version:||Windows XP|
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.
Change History (2)
by , 12 years ago
comment:1 by , 12 years ago
|Priority:||normal → high|
I am also experiencing a similar issue with Maverick SSHD version 1.4.32 - bug# 7757
filezilla debug log during failed directory upload