Help Center/ Anti-DDoS/ API Reference/ API/ Anti-DDoS Management/ Updating Anti-DDoS Defense Policies

Updated on 2024-09-12 GMT+08:00

View PDF

Updating Anti-DDoS Defense Policies

Function

URI

PUT /v1/{project_id}/antiddos/{floating_ip_id}

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	poject id Minimum: 32 Maximum: 64
floating_ip_id	Yes	String	ID corresponding to the EIP of a user

**Table 2** Query Parameters
Parameter	Mandatory	Type	Description
ip	No	String	ip

Request Parameters

**Table 3** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	token Minimum: 32 Maximum: 2097152
Content-Type	Yes	String	Default: application/json;charset=utf8

**Table 4** Request body parameters
Parameter	Mandatory	Type	Description
app_type_id	Yes	Integer	Application type ID.
cleaning_access_pos_id	Yes	Integer	Position ID of access limit during cleaning. The value ranges from 1 to 8 and 33 to 36.
enable_L7	Yes	Boolean	Whether L7 defense has been enabled
http_request_pos_id	Yes	Integer	Position ID of number of HTTP requests. The value ranges from 1 to 15 and 33 to 36.
traffic_pos_id	Yes	Integer	Position ID of traffic. The value ranges from 1 to 9 and 33 to 36.

Response Parameters

Status code: 200

**Table 5** Response body parameters
Parameter	Type	Description
error_code	String	Internal error code
error_msg	String	Internal error description
task_id	String	ID of a task.

Example Requests

{
  "app_type_id" : 0,
  "cleaning_access_pos_id" : 8,
  "enable_L7" : false,
  "http_request_pos_id" : 1,
  "traffic_pos_id" : 1
}

Example Responses

Status code: 200

{
  "error_code" : "10000000",
  "error_msg" : "The task has been received and is being handled",
  "task_id" : "59385d2a-6266-4d3a-9122-a228c530f557"
}