Closed Bug 1112058 Opened 11 years ago Closed 11 years ago

Setting ACL for S3 folder has no effect

Categories

(Infrastructure & Operations :: Tools, task)

Product:
Infrastructure & Operations
Component:
Tools
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: posidron, Unassigned)

Details

Not sure if this is the right component but I got clueless in how to solve this issue. I'm unable to set the ACL for the "Resource" folder in "s3://fuzzing.s3.mozilla.net/" to public. I have tried it with the s3cmd tool like: % s3cmd setacl s3://fuzzing.s3.mozilla.net/Resources/ --acl-public --recursiv but some folders inside "Resources" do not adapt the change ("Resources/Settings" and "Resources/Templates") and are only available for authenticated users. I have also tried to set the ACL with s3fox but it returns me this error for each try in setting a new ACL "Your request was missing a required header". Sadly, there are not many options to play around with in s3fox. How do I make all content for "Resources" public accessible?
Problem disappeared in a mysterious way.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.