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

Empty Directory [Follow-on of ticket #2549] #2559

Closed
cyberduck opened this issue Sep 8, 2008 · 1 comment
Closed

Empty Directory [Follow-on of ticket #2549] #2559

cyberduck opened this issue Sep 8, 2008 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 8, 2008

a8d3559 created the issue

Looking into the submitted tickets, I found a significant number describing the same problem as ticket #2549 (directory looking empty while it is not).

The problem does not come from CyberDuck but rather from some buggy FTP servers.

However, since this problem seems to be rather common, I would like to make the following suggestion :

After issuing a STAT command, if the directory appear to be empty, try to issue a LIST -a (and eventually a LIST) command in order to check if the server is faulty or not.

This extra check will no take time since it will occur only for empty directories (or looking so).

In case of faulty server, the send command can be temporary adjusted.

If the server is O.K., then the extra test can be discarded permanently (for this server).

Best regards

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 9, 2008

@dkocher commented

A fallback mechnism is in place since 3.0.2 (see 0fda43b). The issue with partial directory listings returned by some implementations is also covered in #2549 and fixed as of 96490a9.

Loading

@cyberduck cyberduck closed this Sep 9, 2008
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants