-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
The bucket does not allow ACLs error when copying file to bucket with BucketOwnerEnforced ownership controls #14300
Comments
@dkocher Thank you for the fix. I'm getting various build errors when attempting to test the build. I'm happy to wait for a release, but wanted to test the patch. The errors may be related to dependencies but I think I've set them up correctly. I had to use the Visual Studio 2022 build tools, rather than the 2017 listed
|
You can switch to the snapshot feed in Preferences → Update to test the fix. |
Thank you. I can confirm that the fix is working. |
@dkocher Using snapshot build 8.5.7.39527 it is still working. Thank you very much. |
Describe the bug
I get the
The bucket does not allow ACLs
error when copying or moving files from one AWS S3 bucket to another. The destination bucket has ACLs disabled but the source does not. I've tried setting Default ACL to various values, including None, but still get the same error. There was work to address this issue in the past, e.g. #13386, which is where I first commented on this.To Reproduce
Steps to reproduce the behavior:
enforced
preferred
preferred
and set the ACL to allow public readpreferred
toenforced
Expected behavior
I would expect Cyberduck to detect that the destination has disabled ACLs and so these should not be set after the file contents have been copied.
Screenshots
Desktop (please complete the following information):
Log Files
I've added a debug log file, but tried to clean any details that are not necessary to debug this, like secrets and names of items. If there are details missing that you would like, please let me know.
cyberduck.log
The text was updated successfully, but these errors were encountered: