Attempt to put canned bucket ACL of "public-read" results in "Invalid Request"

[lrm25]

Describe the bug
Direct communication with AWS (after enabling ACLs and public access to the bucket) results in the expected behavior, but attempting to put the ACL via versity results in the following being returned:

An error occurred (InvalidRequest) when calling the PutBucketAcl operation: Invalid Request

To Reproduce

1. Create a bucket in the Amazon S3 console.
2. Select the bucket and select the Permissions tab.
3. Check the Block public access section and select Edit and set Block all public access to off if not already off.
4. Go to the Object Ownership section, select Edit, and select ACLs Enabled and set Object Ownership to Object Writer if this hasn't already been done.
5. Set the AWS_ENDPOINT_URL value to point to the versity gateway, and send the following command: aws --no-verify-ssl s3api put-bucket-acl --bucket <name> --acl public-read

Expected behavior
The request succeeds, and the get-bucket-acl command returns a Grants element similar to the following:

{
     "Grantee": {
         "Type": "Group",
         "URI": "http://acs.amazonaws.com/groups/global/AllUsers"
     },
     "Permission": "READ"
 }

Server Version

Version  : v0.21
Build    : 10ed210
BuildTime: 2024-05-02_11:46:50PM
Darwin Lukes-MacBook-Pro.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:25 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6030 arm64

[jonaustin09]

Thanks for the bug report, I'll take a look. For your information our implementation of Bucket ACLs differ from traditional AWS ACLs. Some features aren't supported in our end. I'll double check this part.