Ben McClelland 5ba5327ba6 fix: s3proxy create bucket always returning BucketAlreadyExists ...

We were using the metadata retrieval to check for existing
buckets during create, and then return either BucketAlreadyExists
or ErrBucketAlreadyOwnedByYou accordingly.

Howver, the metadata retrieval was returning success with a
default ACL when the bucket metadata did not already exist
causing the gateway to always think this bucket existed.

Fix here is to let the metadata retrieval know that we do not
want the default ACL for this case.

2025-07-02 16:29:28 -07:00

..

client.go

use path style

2025-05-06 10:28:16 +08:00

s3.go

fix: s3proxy create bucket always returning BucketAlreadyExists

2025-07-02 16:29:28 -07:00