Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ftp servers signals error to Cyberduck despite succesful file move #1034

Closed
cyberduck opened this issue Feb 20, 2007 · 1 comment
Closed
Assignees
Labels
bug fixed ftp FTP Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

7ef6a8d created the issue

OK, I'm connected to an ftp-server with a personal account.
When I move a file (or folder) within the ftp-account (not transfer to/from ftp-server) to another folder, Cyberduck displays an error popup saying:

FTP Error: Cannot rename file 
/myfolder/myfilename 
renamed

In the Cyberduck browser the file (or folder) seems un-moved, but
when I hit the Refresh button, I see that the operation has ... SUCCEDED.
The last line in red ("renamed") hints that the operation was succesful, but why the error notification?

This happens with all files/folders on this server...
Everytime, all the time.
Mac OS X 10.3.9.

Server transcript:

NOOP
200 cool
CWD /private
250 switched to private
RNFR to-do #2.txt
350 proceed with the destination name
RNTO /private/bup_2005/to-do #2.txt
200 renamed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See 2857.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed ftp FTP Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants