Querying Configured Anti-DDoS Defense Policies
Function
Querying Configured Anti-DDoS Defense Policies
Debugging
You can use API Explorer to debug this API.
URI
GET /v1/{project_id}/antiddos/{floating_ip_id}
| 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 |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| ip | No | String | IP address. |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | Yes | String | token Minimum: 32 Maximum: 2097152 |
| Content-Type | Yes | String | Default: application/json;charset=utf8 |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| enable_L7 | Boolean | Whether L7 defense has been enabled |
| traffic_pos_id | Long | Position ID of traffic. The value ranges from 1 to 9 and 33 to 36. |
| http_request_pos_id | Long | Position ID of number of HTTP requests. The value ranges from 1 to 15 and 33 to 36. |
| cleaning_access_pos_id | Long | Position ID of access limit during cleaning. The value ranges from 1 to 8 and 33 to 36. |
| app_type_id | Long | Application type ID. |
Example Requests
None
Example Responses
None
Status Codes
| Status Code | Description |
|---|---|
| 200 | OK |
Error Codes
See Error Codes.
Last Article: Querying Weekly Defense Statistics
Next Article: Updating Anti-DDoS Defense Policies
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.