-
Notifications
You must be signed in to change notification settings - Fork 180
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 put object acl without a policy #1617
Comments
@mkleint does the code above work against S3? The API clearly states:
https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjectAcl.html So the request should fail on S3 as well. |
ah! |
The old code I'm migrating was using java aws client v2 with following code
I assume it works, as we running that in production. unfortunately that old code is not using s3mock in CI to test. the new code we creating now is doing the same and I've tried to add component test to verify in CI. I've tried to create the aws cli equivalent to test against the s3mock and to report as issue. No idea if the java client is adding some kind of dummy request body or not. |
@mkleint I just released 3.5.1 that supports canned ACLs. |
great, thank you. works perfectly now |
aws --profile okta s3api put-object-acl --acl "bucket-owner-full-control" --key "data.txt" --bucket video-nonprod --endpoint-url=http://localhost:9090 --debug
our code performs a java equivalent of the above. s3mock returns 400, I assume because the request body cannot be parsed, because we don't specify the policy
The text was updated successfully, but these errors were encountered: