Updated on 2023-09-08 GMT+08:00

Updating a Geolocation Access Control Rule

Function

Updating a Geolocation Access Control Rule

URI

PUT /v1/{project_id}/waf/policy/{policy_id}/geoip/{rule_id}

Table 1 Path Parameters

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 (value of the id field in the response body).

rule_id

Yes

String

ID of the geolocation access control rule. You can obtain the rule ID by calling ListGeoipRule API which is used to query the list of geolocation access control rules. The rule ID is included the id field in the response body.

Table 2 Query Parameters

Parameter

Mandatory

Type

Description

enterprise_project_id

No

String

You can obtain the ID by calling the ListEnterpriseProject API of EPS.

Request Parameters

Table 3 Request header 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

Table 4 Request body parameters

Parameter

Mandatory

Type

Description

name

No

String

Name of the geolocation access control rue

description

No

String

description

geoip

Yes

String

Locations that can be configured in the geolocation access control rule: (CN: China, South Africa: South Africa, Mexico: Mexico, Peru: Peru, Indonesia: Indonesia, GD Guangdong, FJ: Fujian, JL: Jilin, LN: Liaoning, TW: Taiwan (China), GZ: Guizhou, AH: Anhui, HL: Heilongjiang, HA: Henan, SC: Sichuan, HE: Hebei, YN: Yunnan, HB: Hubei, HI: Hainan, QH: Qinghai, HN: Hunan, JX: Jiangxi, SX: Shanxi, SN: Shaanxi, ZJ: Zhejiang, GS: Gansu, JS: Jiangsu, SD: Shandong, BJ: Beijing, SH: Shanghai, TJ: Tianjin, CQ: Chongqing, MO: Macao (China), HK: Hong Kong (China), NX: Ningxia, GX: Guangxi, XJ: Xinjiang, XZ: Tibet, NM: Inner Mongolia

white

Yes

Integer

Protective action

  • 0: WAF blocks requests that hit the rule.

  • 1: WAF allows requests that hit the rule.

  • 2: WAF only record requests that hit the rule.

Response Parameters

Status code: 200

Table 5 Response body parameters

Parameter

Type

Description

id

String

Rule ID

name

String

Name of the geolocation access control rue

description

String

Description

policyid

String

Policy ID

geoip

String

Locations that can be configured in the geolocation access control rule: (CN: China, South Africa: South Africa, Mexico: Mexico, Peru: Peru, Indonesia: Indonesia, GD Guangdong, FJ: Fujian, JL: Jilin, LN: Liaoning, TW: Taiwan (China), GZ: Guizhou, AH: Anhui, HL: Heilongjiang, HA: Henan, SC: Sichuan, HE: Hebei, YN: Yunnan, HB: Hubei, HI: Hainan, QH: Qinghai, HN: Hunan, JX: Jiangxi, SX: Shanxi, SN: Shaanxi, ZJ: Zhejiang, GS: Gansu, JS: Jiangsu, SD: Shandong, BJ: Beijing, SH: Shanghai, TJ: Tianjin, CQ: Chongqing, MO: Macao (China), HK: Hong Kong (China), NX: Ningxia, GX: Guangxi, XJ: Xinjiang, XZ: Tibet, NM: Inner Mongolia

white

Integer

Protective action

  • 0: WAF blocks requests that hit the rule.

  • 1: WAF allows requests that hit the rule.

  • 2: WAF only record requests that hit the rule.

Status code: 400

Table 6 Response body parameters

Parameter

Type

Description

error_code

String

Error code

error_msg

String

Error message

Status code: 401

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

Error code

error_msg

String

Error message

Status code: 500

Table 8 Response body parameters

Parameter

Type

Description

error_code

String

Error code

error_msg

String

Error message

Example Requests

PUT https://{Endpoint}/v1/{project_id}/waf/policy/{policy_id}/geoip/{rule_id}?enterprise_project_id=0

{
  "white" : 0,
  "name" : "demo",
  "geoip" : "BJ|Afghanistan"
}

Example Responses

Status code: 200

Request succeeded.

{
  "id" : "02dafa406c4941368a1037b020f15a53",
  "policyid" : "38ff0cb9a10e4d5293c642bc0350fa6d",
  "name" : "demo",
  "description" : "demo",
  "geoip" : "BJ|Afghanistan",
  "white" : 0
}

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.