0038-00000002

Problem description

The x-oss-defender-instance header does not exist in the UpdateUserAntiDDosInfo request.

Causes

You initiated an UpdateUserAntiDDosInfo request to change the status of an Anti-DDoS instance. However, the x-oss-defender-instance header that specifies the ID of the instance does not exist in the request.

Examples

For example, you initiate the following request:

POST /?antiDDos HTTP/1.1
Date:  GMT Date
Host: oss-cn-hangzhou.aliyuncs.com
Authorization: SignatureValue
x-oss-defender-instance:
x-oss-defender-status: HaltDefending

The x-oss-defender-instance header is required and cannot be left empty. In this example, the header is empty, which does not conform to the specification of the UpdateUserAntiDDosInfo operation. As a result, an error is returned.

Solutions

Make sure that the UpdateUserAntiDDosInfo request contains the required x-oss-defender-instance header and a valid value is specified for the header. The following code shows a valid request:

POST /?antiDDos HTTP/1.1
Date:  GMT Date
Host: oss-cn-hangzhou.aliyuncs.com
Authorization: SignatureValue
x-oss-defender-instance: cbcac8d2-4f75-4d6d-9f2e-c3447f73****
x-oss-defender-status: HaltDefending

For more information about how to configure Anti-DDoS instances in the Object Storage Service (OSS) console, see OSS DDoS protection.

References

UpdateUserAntiDDosInfo