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 uploads fail when policy denies "s3:PutObjectAcl" #7356

Closed
cyberduck opened this issue Jul 19, 2013 · 4 comments
Closed

S3 uploads fail when policy denies "s3:PutObjectAcl" #7356

cyberduck opened this issue Jul 19, 2013 · 4 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

15558da created the issue

Maybe Cyberduck should not include the x-amz-acl and x-amz-storage-class headers in PUT object by default, because the user might not be able to manipulate the ACL and the upload will fail. Either set the ACL afterwards in different request, or make the defaults key "s3.key.acl.default" and "s3.location" optional.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Unfortunately this would triple the protocol overhead.

@cyberduck
Copy link
Collaborator Author

15558da commented

What about adding a "default" option to the selector in preferences that makes it not to send these headers?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 petr tichý]:

What about adding a "default" option to the selector in preferences that makes it not to send these headers?

With d7c054e the ACL headers are only sent when Change Permissions is checked in Preferences → Transfers → Permissions → Change permissions.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 25f3c43. Set ACLs in post upload only if Change Permissions is selected in Preferences → Upload. Only set storage class when set to other than STANDARD.

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

No branches or pull requests

2 participants