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

Cannot delete files with S3 protocol (GreenQloud) #6598

Closed
cyberduck opened this issue Mar 23, 2012 · 6 comments
Closed

Cannot delete files with S3 protocol (GreenQloud) #6598

cyberduck opened this issue Mar 23, 2012 · 6 comments
Assignees
Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

649e914 created the issue

It worked fine to delete files in 4.2.1 but is broken in the latest snapshot release (9483). I get a "forbidden" error message. The test I did was to upload a file with no special characters to a bucket with no special characters and then I tried deleting it again. I have a feeling the command is trying to delete the wrong path or something has changed in the delete method for S3 protocol in this release.

POST /?delete HTTP/1.1
Date: Fri, 23 Mar 2012 15:29:53 GMT
Content-MD5: ygJzdhZmyIr1E/wSYW6dhA==
Content-Type: text/plain
Authorization: AWS VnFMV2s4YXlyVnlUS2FVeUlrNnh2OTVXcURWOW9v:D6N7UFysBXrX6xsDQTpoJb8V9C8=
Content-Length: 120
Host: permissionstest.s.greenqloud.com:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.2.1 (Mac OS X/10.7.3) (i386)
Expect: 100-continue
HTTP/1.1 403 Forbidden
Date: Fri, 23 Mar 2012 15:29:50 GMT
Server: RestServer/1.0
Content-Length: 110
Content-Type: application/xml
Cache-Control: no-cache
Connection: close
@cyberduck
Copy link
Collaborator Author

649e914 commented

As suggested:
"That is most possibly related to #6438 implementing the new Multiple File Delete from AWS."

GreenQloud doesn't support versioning or multi factor authentication (yet and possibly won't). If it's simply a matter of not having the service implemented on our end and not a bug I suggest the delete method tries this method first (for the first file to delete) and if that fails to switch to the old method for the remainder of the session.

cheers
Eiki

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:2 greenqloud]:

As suggested:
"That is most possibly related to #6438 implementing the new Multiple File Delete from AWS."

GreenQloud doesn't support versioning or multi factor authentication (yet and possibly won't). If it's simply a matter of not having the service implemented on our end and not a bug I suggest the delete method tries this method first (for the first file to delete) and if that fails to switch to the old method for the remainder of the session.

cheers
Eiki

This is not per se a feature related to versioning or MFA we support. Refer to S3 API documentation.

The Multi-Object Delete operation enables you to delete multiple objects from a bucket using a single HTTP request

This was introduced by AWS in the 07 December 2011 release.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:2 greenqloud]:

…if that fails to switch to the old method for the remainder of the session.

I don't think I will support multiple paths here. You will have to bite the bullet and try to catch up on AWS here.

@cyberduck
Copy link
Collaborator Author

649e914 commented

I see...my mistake. We will definately add that method but can the next release however have the fallback until we do catch up, I suspect some other S3 compatible services will fail as well.

When is the next release scheduled anyway?

Also do you plan to support the standardised SNIA CDMI storage protocol? http://www.snia.org/cdmi

cheers
eiki

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:6 greenqloud]:

I see...my mistake. We will definately add that method but can the next release however have the fallback until we do catch up, I suspect some other S3 compatible services will fail as well.

When is the next release scheduled anyway?

Will take another month.

Also do you plan to support the standardised SNIA CDMI storage protocol? http://www.snia.org/cdmi

Admittedly I haven't looked into this yet. I heard about Scality supporting this but don't know about anyone else. You might want to open an enhancement request so we can track this.

cheers
eiki

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed in b1898af.

@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 high priority s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants