0038-00000006

Problem description

The status of the Anti-DDoS instance specified in the request is invalid.

Causes

You initiated an OSS DDoS protection related request, such as UpdateBucketAntiDDosInfo, but used the x-oss-defender-status header to specify an invalid status for an Anti-DDoS instance.

For an UpdateBucketAntiDDosInfo request, supported Anti-DDoS instance status include:

• Init: specifies that the instance is being initialized. You must specify the custom domain name that you want to protect.

• Defending: specifies that the instance is in effect and protection is enabled. You can choose whether to specify the custom domain name that you want to protect.

• HaltDefending: specifies that the instance is released and protection is disabled. You do not need to specify the custom domain name that you want to protect.

For an UpdateUserAntiDDosInfo request, only the HaltDefending status is supported.

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: cbcac8d2-4f75-4d6d-9f2e-c3447f73****
x-oss-defender-status: Halt

The preceding request is an UpdateUserAntiDDosInfo request. The value of the x-oss-defender-status request header must be HaltDefending. An error is returned for the request because the value is invalid.

Solutions

Make sure that the value specified for the x-oss-defender-status header in the request is valid. The following code provides an example.

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 DDoS protection in the OSS console, see OSS DDoS protection.

References

• UpdateUserAntiDDosInfo

• UpdateBucketAntiDDosInfo