Canned ACLs seem to be missing in s3 client

[DreamHost]

I couldn't find canned ACLs mentioned in the s3 code, and grep'ing the source tree didn't reveal anything.

Docs:
  http://docs.amazonwebservices.com/AmazonS3/2006-03-01/dev/CannedACL.html

"Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined a set of grantees and permissions. You specify a canned ACL in your request using the x-amz-acl request header. When Amazon S3 receives a request with a canned ACL in the request, it adds the predefined grants to the ACL of the resource. The following table lists the set of canned ACLs and the associated predefined grants."

Canned ACL Names:
 * private
 * public-read
 * public-read-write
 * authenticated-read
 * bucket-owner-read
 * bucket-owner-full-control
 * log-delivery-write

"When creating an object or a bucket, you cannot specify an ACL. instead, you can specify the canned ACL."

[Duncan McGreggor (oubiwann)]

After some pocking around in the doc and AWS docs, the best approach seems to be to extend the put_<bucket/object>_acl methods: where a policy parameter is passed, it will also be possible to pass a canned ACL string. This branch will require some minor plumbing changes to accomodate that usage, however.

[Duncan McGreggor (oubiwann)]

In particular, the minor plumbing changes will require support for the amz_header parameter. See bug #972432.