Problem description
The time when a request is initiated to access OSS objects by using a signed URL that contains a V4 signature is not within the validity period of the URL.
Causes
The time when a request is initiated to access OSS objects by using a signed URL that contains a V4 signature is earlier than the start time of the validity period of the signed URL.
Examples
The start time of the validity period of the signed URL specified by x-oss-date is 20231220T083018Z. However, the actual time when the request is initiated is 20231220T081516Z.
GET /oss.jpg?x-oss-additional-headers=host&x-oss-credential=accesskeyid%2F20231203%2Fcn-hangzhou%2Foss%2Faliyun_v4_request&x-oss-date=20231220T083018Z&x-oss-expires=86400&x-oss-signature=2c6****&x-oss-signature-version=OSS4-HMAC-SHA256
Host: oss-example.oss-cn-hangzhou.aliyuncs.comSolutions
Make sure that the time when a request is initiated to access OSS objects by using a signed URL that contains a V4 signature is within the validity period of the signed URL. When you configure the time when a request is initiated by specifying x-oss-date, allow an offset of up to 15 minutes after the request is initiated.
For example, if you set x-oss-date to 20231220T083018Z, the actual time when a request is initiated by using a signed URL that contains a V4 signature cannot be earlier than 20231220T081518Z.