Deleting a Global Protection Whitelist (Formerly False Alarm Masking) Rule
Function
This API is used to delete a global protection whitelist (formerly false alarm masking) rule.
URI
DELETE /v1/{project_id}/waf/policy/{policy_id}/ignore/{rule_id}
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. To obtain it, go to Cloud management console and hover the cursor over your username. On the displayed window, choose My Credentials.Then, in the Projects area, view Project ID of the corresponding project. |
policy_id |
Yes |
String |
Policy ID. It can be obtained by calling the ListPolicy API. |
rule_id |
Yes |
String |
ID of a false alarm masking rule. You can obtain the rule ID from the id field in the response body of the ListIgnoreRule API, which is used for querying false alarm masking rules. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
enterprise_project_id |
No |
String |
You can obtain the ID by calling the ListEnterpriseProject API of EPS. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
User token. It can be obtained by calling the IAM API (value of X-Subject-Token in the response header). |
Content-Type |
Yes |
String |
Content type. Default: application/json;charset=utf8 |
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
id |
String |
Rule ID |
policyid |
String |
Policy ID |
timestamp |
Long |
Timestamp the rule was created. |
description |
String |
Rule Description |
status |
Integer |
Rule status. The value can be 0 or 1.
|
url |
String |
The path for false masking alarms. This parameter is available only when mode is set to 0. |
rule |
String |
ID of the built-in rule to be masked. You can query the rule ID by choosing Policies > Policy Name > Basic Web Protection > Protection Rules on the WAF console or on the event details page. |
mode |
Integer |
Version number. The value can be 0 or 1. 0: indicates the old version V1. 1 indicates the new version V2. When the value of mode is 0, the conditions field does not exist, but the url and url_logic fields exist. When the value of mode is 1, the url and url_logic fields do not exist, but the conditions field exists. |
url_logic |
String |
URL match logic |
conditions |
Array of Condition objects |
Filter |
domains |
Array of strings |
Protected domain name or website |
Parameter |
Type |
Description |
---|---|---|
category |
String |
Field type. The value can be ip, url, params, cookie, or header. |
contents |
Array of strings |
Content. The array length must be 1. The content format varies depending on field types. For example, if the field type is ip, the value must be an IP address or IP address range. If the field type is url, the value must be a URL in standard format. If the field type is params, cookie, or header, the content format is not limited. |
logic_operation |
String |
The matching logic varies depending on the field type. For example, if the field type is ip, the logic can be equal or not_equal. If the field type is url, params, cookie, or header, the logic can be equal, not_equal, contain, not_contain, prefix, not_prefix, suffix, not_suffix. |
check_all_indexes_logic |
Integer |
This parameter is reserved and can be ignored. |
index |
String |
If the field type is ip and the subfield is the client IP address, the index parameter does not exist. If the subfield type is X-Forwarded-For, the value is x-forwarded-for. If the field type is params, header, or cookie, and the subfield is user-defined, the value of index is the user-defined subfield. |
Status code: 400
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code |
error_msg |
String |
Error message |
Status code: 401
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code |
error_msg |
String |
Error message |
Status code: 500
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code |
error_msg |
String |
Error message |
Example Requests
The following example shows how to delete a global whitelist protect (the formerly false alarm masking) rule Details about the rule are specified by project_id, policy_id, and rule_id.
DELETE https://{Endpoint}/v1/{project_id}/waf/policy/{policy_id}/ignore/{rule_id}
Example Responses
Status code: 200
Request succeeded.
{ "id" : "40484384970948d79fffe4e4ae1fc54d", "policyid" : "f385eceedf7c4c34a4d1def19eafbe85", "timestamp" : 1650512535222, "description" : "demo", "status" : 1, "rule" : "091004", "mode" : 1, "conditions" : [ { "category" : "ip", "contents" : [ "x.x.x.x" ], "logic_operation" : "equal" } ], "domain" : [ "we.test.418lab.cn" ] }
Status Codes
Status Code |
Description |
---|---|
200 |
Request succeeded. |
400 |
Request failed. |
401 |
The token does not have required permissions. |
500 |
Internal server error. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.