Problem description
The request uses the wrong signature method for the operation.
Causes
OSS operations require one of two signature methods. Using the wrong method for an operation triggers this error.
Scenario 1: The operation requires the signature in URL query string parameters (signed URL), but the request includes the signature in the
Authorizationheader instead.Scenario 2: The operation requires the signature in the
Authorizationheader, but the request includes the signature as URL query string parameters instead.
Examples
Scenario 1 — signature in `Authorization` header when a signed URL is required:
GET /test_rtmp_live/test.m3u8?x-oss-process=hls/sign HTTP/1.0
Date: Tue, 20 Dec 2022 08:48:18 GMT
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Authorization: AWS qn6q**************:77Dv****************
x-oss-security-token: CAIS**************Scenario 2 — signature in URL query string when an `Authorization` header is required:
GET /test_rtmp_live/test.m3u8?x-oss-process=hls/sign&OSSAccessKeyId=nz2p********&Expires=1141889120&Signature=vjby********&security-token=CAIS************** HTTP/1.0
Date: Tue, 20 Dec 2022 08:48:18 GMT
Host: oss-example.oss-cn-hangzhou.aliyuncs.comSolutions
Scenario 1: Move the signature to the URL query string parameters and remove the Authorization header.
GET /test_rtmp_live/test.m3u8?x-oss-process=hls/sign&OSSAccessKeyId=nz2p********&Expires=1141889120&Signature=vjby********&security-token=CAIS************** HTTP/1.0
Date: Tue, 20 Dec 2022 08:48:18 GMT
Host: oss-example.oss-cn-hangzhou.aliyuncs.comFor details on constructing a signed URL, see Add signatures to URLs.
Scenario 2: Move the signature to the Authorization header and remove the signature parameters from the URL.
GET /oss.jpg HTTP/1.0
Date: Tue, 20 Dec 2022 08:48:18 GMT
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Authorization: AWS qn6q**************:77Dv****************
x-oss-security-token: CAIS**************For details on constructing the Authorization header, see Add signatures to headers.