Issue description
The Credential field in the Authorization request header is missing.
Causes
You initiated a request that uses an Amazon S3-compatible V4 signature, but the Credential field in the Authorization request header is missing.
Examples
You initiated a request that uses an Amazon S3-compatible V4 signature, but the Credential field in the Authorization request header is missing.
GET /test.txt HTTP/1.0
Date: Tue, 20 Dec 2022 08:48:18 GMT
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Authorization:AWS4-HMAC-SHA256 SignedHeaders=host;x-amz-content-sha256;x-amz-date,Signature=34*****
x-amz-content-sha256: abc***
x-amz-date: 20221220T084818Z
x-oss-s3-compat: trueSolutions
Make sure that the Authorization request header is complete and correctly calculated. The Credential field is in the following format: <YOUR-AKID>/YYYYMMDD/REGION/SERVICE/aws4_request. The following code provides an example on how to correctly specify the Authorization request header:
GET /test.txt HTTP/1.0
Date: Tue, 20 Dec 2022 08:48:18 GMT
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Authorization:AWS4-HMAC-SHA256 Credential=LTAI****************/20221220/us-east-1/s3/aws4_request,SignedHeaders=host;x-amz-content-sha256;x-amz-date,Signature=34****
x-amz-content-sha256: abc****
x-amz-date: 20221220T084818Z
x-oss-s3-compat: trueWe recommend that you use Amazon S3 SDKs to initiate the request. For more information, see Use Amazon S3 SDKs to access OSS.