Unmatched Signatures (SDK for Node.js)

Updated on 2024-11-26 GMT+08:00

View PDF

Problem: The HTTP status code obtained from CommonMsg.Status was 403, and the OBS server-side error code obtained from CommonMsg.Code was SignatureDoesNotMatch.

Solution:

Check whether a bucket name was added before the endpoint. This will lead to a signature mismatch.
Ensure that the AK and SK matched, were both correctly specified, and were the same as those used in the request.

Check StringToSign.

The structure of StringToSign should be as follows:

HTTP-Verb + "\n" + Content-MD5 + "\n" + Content-Type + "\n" + Date + "\n" + CanonicalizedHeaders + CanonicalizedResource

Parent topic: Troubleshooting (SDK for Node.js)

Previous topic: Connection Timeout (SDK for Node.js)

Next topic: FAQs (SDK for Node.js)

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel