Title:
Calling StoreAddACL before StoreSetMetadata doesn't commit the new ACL to S3
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/Duplicate
Reporter/Name(from Bugbase): Indy Griffiths / Indy Griffiths (Indy Griffiths)
Created: 12/07/2014
Components: File Management, VFS-S3
Versions: 11.0
Failure Type: Incorrect w/Workaround
Found In Build/Fixed In Build: CF11_Final /
Priority/Frequency: Normal / Some users will encounter
Locale/System: ALL / Platforms All
Vote Count: 1
Duplicate ID: CF-3043124
Problem Description:
When working with S3 objects, calling StoreAddACL before StoreSetMetadata doesn't commit the new ACL to the S3 object.
Related to bug #3043124
Steps to Reproduce:
1. Make a call to StoreAddACL to set a custom ACL for a S3 object
2. Make a call to StoreSetMetadata to set a custom piece of metadata for the object (in this example a custom Content-Type header)
<cfset StoreAddACL("s3://bucket/object.jpg", [{group="all", permission="read"}])>
<cfset StoreSetMetadata("s3://bucket/object.jpg", {"img_id"="12345"})>
Actual Result:
The ACL specified in StoreAddACL isn't applied to the object.
Expected Result:
The new ACL specified in StoreAddACL is applied to the S3 object. In the above example, it's expected for the read permission to be applied to the 'all' group.
Any Workarounds:
Place the call to StoreSetMetadata before StoreAddACL.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3863487
External Customer Info:
External Company:
External Customer Name: indy-griffiths
External Customer Email:
External Test Config: My Hardware and Environment details:
ColdFusion 11,0,01,291346
Windows 8.1Attachments:
Comments: