Actions
Bug #44987
closedrgw: anonymous object should belong to the bucket owner
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
After set one bucket full_control to anyone, we can put a object without signature.
However, after putting a object without signature, I can not set the acl of it using s3cmd with the 403 error.
Comparing with the s3 public write bucket, I found out that the anonymous object belong to the bucket owner in s3,
while it belong to anonymous user in rgw, which made the 403 error.
The cmd I used is in the cmd.txt file.
Files
Updated by Abhishek Lekshmanan about 4 years ago
- Status changed from New to Fix Under Review
Updated by J. Eric Ivancich over 3 years ago
- Status changed from Fix Under Review to Resolved
Actions