Problem description
The SignDate field in the x-oss-credential header of a PostObject request contains an invalid value.
Causes
This error occurs when a PostObject request that includes a V4 signature has an invalid SignDate value in the x-oss-credential header. Two distinct conditions trigger this error:
Invalid format: The
SignDatevalue is not in%Y%m%dformat (for example,20240315).Clock skew too large: The difference between the
SignDatevalue and the local time exceeds the allowed threshold.
Examples
Cause 1: Invalid format
The SignDate field uses an incorrect date format, such as 2024-03-15 or 15/03/2024 instead of the required 20240315.
Cause 2: Clock skew too large
The local system clock is out of sync. The SignDate value differs from the local time by more than the allowed amount, causing the request to be rejected even if the format is correct.
Solutions
The fix depends on which cause applies.
If the format is invalid, set the SignDate value to the %Y%m%d format. For example, March 15, 2024 must be written as 20240315.
If the clock skew is too large, sync your local system clock to a reliable time source so that the SignDate value matches local time within the allowed threshold.
For the full x-oss-credential format and PostObject signing requirements, see PostObject.