Problem description
When you call bucket-level operations such as PutBucket, PutBucketAcl, PutBucketPolicy, or PutBucketLifecycle, OSS returns HTTP status code 403.
Causes
Bucket-level operations do not support V1 signed URLs. If the request carries signature information as URL query parameters (OSSAccessKeyId, Expires, Signature), OSS rejects the request with a 403 error. For a full list of bucket-level operations, see Bucket operations.
Examples
The following PutBucketAcl request fails because the signature is embedded in the URL query string instead of the Authorization header:
PUT /?acl&OSSAccessKeyId=nz2p****&Expires=abc&Signature=vjbyPxybdZaNmGa%2ByT272YEAiv**** HTTP/1.1
x-oss-acl: Permission
Host: BucketName.oss-cn-hangzhou.aliyuncs.com
Date: GMT DateSolutions
To call bucket-level operations, use one of the following approaches:
Authorization header: Include the signature in the
Authorizationheader instead of the URL query string. See Include signatures in the Authorization header.OSS console: Perform the operation through the OSS console.