Bug #17971
closedbucket acl all user write
0%
Description
When I set the bucket all user acl permission write.
Then use the postman to send a put request to the bucket, to override the object inside.
At this time, the bucket owner can not read the covered object.
Updated by Jiang Yu over 7 years ago
test Methods:
1.set a bucket to all user write permissions
2.use the postman to send a put request, in the bucket to create a file
3.gets the acl of the created file
4.bug recurrence
Updated by Yehuda Sadeh over 7 years ago
when a user uploads an object, that user is the owner of that object. This PR changes this semantics and it's incorrect. The question that we have is who should be the owner of an object created by the anonymous user. It can either be the bucket owner, or the anonymous group. It might be that the actual issue is that when the all-users group is the owner, any authenticated user cannot read that object.
Updated by Jiang Yu over 7 years ago
Thank you, I understand. I think, in fact, this is normal. I tested an anonymous user to delete, the object is to operate.