new test case suggestion: bucket creation with ACL about s3-tests HOT 3 OPEN

Hi Tom,

We will include a test that sets a bucket acl, namely public read-write, in
the test of POST object.

Caleb
On Oct 16, 2012 8:21 PM, "Tom Fifield" [email protected] wrote:

Hi,

one common action for many s3 clients, such as cyberduck, is to set ACLs
for a bucket at the same time as it is being created. This would be a
valuable test case, as the having the X-Amz-Acl header set could be treated
differently when creating a bucket - it caught me out when working on
swift, at least :)

I'm not sure what boto sends, but here's an example request from cuberduck:

PUT /lol/ HTTP/1.1
Date: Tue, 16 Oct 2012 22:56:57 GMT
x-amz-acl: public-read
Content-Type: application/octet-stream
Authorization: AWS admin:admin:qibESADS8jtU8aZTJa2K0KJqo1g=
Content-Length: 0
Host: 192.168.1.20:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.2.1 (Mac OS X/10.8.2) (i386)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2.

from s3-tests.

We shouldn't bundle this in the POST, it should have its own tests (maybe part of the bucket creation). I'm not completely sure that we don't test it yet though.

from s3-tests.

HI,

Thanks for looking into this.

Individually, you do test the functionality, i.e.:

1. create bucket & check it is created
2. set acl & check it is set

However, this suggestion for a new test is to set the x-amz-acl header on bucket creation - a single call, rather than first creating the bucket, then setting the acl.

from s3-tests.