s3cmd - put command does not work on a container with correct acl

[Peter Coppens]

It seems that s3cmd, when doing a put object in a container, first invokes a HTTP GET on a /container/?location URL but this does not seem to be allowed.

In the log I find GET /container/%3Flocation HTTP/1.0 403

Executing the same put object with s3curl works fine.

So, I guess it would be nice if, based on the ACL, such a GET /container/?location would pass without a 403.