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

Jump to bottom

Cannot delete S3 "folders" #10101

Closed
cyberduck opened this issue Oct 6, 2017 · 2 comments
Closed

Cannot delete S3 "folders" #10101

cyberduck opened this issue Oct 6, 2017 · 2 comments
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
6.3

Comments

@cyberduck
Copy link
Collaborator

cd80978 created the issue

S3 doesn't really have folders, only single files grouped according to / characters contained in their keys.
However when clicking a folder and selecting Delete from the actions, I remember Cyberduck would recursively delete all contained keys.
Now instead it seems to consider the folder as a file in its own right, failing:

HEAD /23435/ HTTP/1.1
Date: Fri, 06 Oct 2017 16:29:02 GMT
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Host: elife-striking-images.s3.amazonaws.com
x-amz-date: 20171006T162902Z
Authorization: ********
Connection: Keep-Alive
User-Agent: Cyberduck/6.2.6.26405 (Mac OS X/10.10.5) (x86_64)
HTTP/1.1 404 Not Found
x-amz-request-id: B06CBAA2F4FF02F1
x-amz-id-2: js/k9zPFoKbXjNgFChyqk8cwso+jfZ6tD7by4Xjx7KhoiRvTUhq6D7NYvaBM/C5fTM5375bNHes=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Fri, 06 Oct 2017 16:29:01 GMT
Server: AmazonS3

The workaround is to go inside the folder and ,manually delete all the files, but that shouldn't be necessary.
Version 6.2.6 on Mac OS X.

Attachments
@cyberduck
Copy link
Collaborator Author

11ee930 commented

I'm dealing with this issue as well. We have versioning on buckets, and a "directory" gets "renamed" or deleted yet it continues to show up in the Cyberduck interface. You try to delete it and it gives you an error. It does not show up in the listing if you use the s3 cli. It doesn't show up in the aws dashboard unless you show versions.

I would expect if you had "show hidden files" turned off this should at least be hidden, and if hidden files was enabled it should be displayed differently to indicate it isn't actually there. It causes a lot of confusion with multiple people accessing a bucket as they are re-uploading things or placing them with previously deleted paths.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In e577f25.

@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.
Assignees

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
6.3
Development

No branches or pull requests
2 participants
@dkocher @cyberduck