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

S3 Bug with no name folders #3332

Closed
cyberduck opened this issue Jul 15, 2009 · 3 comments
Closed

S3 Bug with no name folders #3332

cyberduck opened this issue Jul 15, 2009 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 15, 2009

7b42e8d created the issue

Just wanted to let you know that cyberduck crashes when there is a directory without a name in a bucket on S3. Im on 10.5.6 (osx) and 3.2.1(cyberduck). At first i didnt know why it kept crashing then I used another S3 client, saw there was a directory without a name, deleted it then opened cyberduck, went to the parent directory of the no-name directory and everything was fine now in cyberduck (no crashing) since the no-name directory was gone.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 15, 2009

@dkocher commented

What do you mean with a directory without a name?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 15, 2009

@dkocher commented

S3 allows you to create an object like s3.amazonaws.com/bucketname/5/images/{directory-without-a-name}/image.jpg

or s3.amazonaws.com/bucketname/5/images//image.jpg

I dont know why this should be possible with S3 but when cyberduck was crashing
i used another S3 client and found in the images 'directory' 3 'directories' named: 15, 14, an one with no name.

After i deleted the no name 'directory' cyberduck stopped crashing.

Looks very similar like issue #2575.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 12, 2009

@dkocher commented

I assume a duplicate of #3347.

Loading

@cyberduck cyberduck closed this Aug 12, 2009
@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