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
Failure to read attributes of symbolic link #8519
Comments
We are handling non existing symbolic targets gracefully and ignoring errors when determine the symbolic link target cannot be found. But this looks like the SFTP server is returning a |
I am on your side WRT "the SFTP server is returning a NO_SUCH_FILE for the symbolic link file itself for the READLINK we send". But I think you are not handling non existing symbolic targets gracefully and you are not ignoring errors when determine the symbolic link target cannot be found. I can honestly assure you you don't, as I don't see any directory listing displayed at all, Can you construct such a situation yourself, Not that I really depend on this issue being solved at all |
We have a test case for this in [source:trunk/test/ch/cyberduck/core/sftp/SFTPListServiceTest.java#L58]. |
Replying to [comment:4 dkocher]:
We only expect the server to return an error response when we try to |
"Business" is a symlink within subdir "home". |
I am connecting to an SFTP server (actually a Linux machine running BusyBox),
almost everything is fine ;-)
I am trying to navigate through the directories,
I am entering a directory with symlinks,
and there is the problem, cyberduck says:
Failure to read attributes of SYMLINK.[[br]]
No such file. Please contact your web hosting service provider for assistance.
I am prevented to get the directory content listed,
I also cannot change into a subdirectory,
I am stuck.
But when I log into that machine using SSH,
I can successfully do "cd" and "ls" and everything,
no problem at all.
Attachments
Screen_Shot.20150123171913.png
(96.7 KiB)Screen_Shot.20150123172219.png
(52.2 KiB)The text was updated successfully, but these errors were encountered: