Queries the configurations of a forwarding rule.
Operation Description
You can call the DescribeWebRules operation to query the configurations of the forwarding rules that you create for a website by page. The configurations include the protocol type, origin server address, HTTPS configuration, and IP address blacklist.
Before you call this operation, you must have created forwarding rules by calling the CreateWebRule operation.
Limits
You can call this operation up to 50 times per second per account. If the number of the calls per second exceeds the limit, throttling is triggered. As a result, your business may be affected. We recommend that you take note of the limit when you call this operation.
Authorization information
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ResourceGroupId | string | No | The ID of the resource group to which the instance belongs in Resource Management. If you do not configure this parameter, the instance belongs to the default resource group. | rg-acfm2pz25js**** |
Domain | string | No | The domain name of the website that you want to query. NoteA forwarding rule must be configured for the domain name. You can call the DescribeDomains operation to query the domain names for which forwarding rules are configured. | example.com |
Cname | string | No | The CNAME to query. | kzmk7b8tt351****.aliyunddos1014**** |
QueryDomainPattern | string | No | The match mode. Valid values:
| exact |
PageNumber | integer | No | The number of the page to return. Default value: 1. | 1 |
PageSize | integer | Yes | The number of entries to return on each page. | 10 |
InstanceIds | array | No | An array that consists of the IDs of instances to query. | |
string | No | The ID of instance N to query. The maximum value of N is 200. You can specify up to 200 instances. Separate the IDs of multiple instances with commas (,). NoteYou can call the DescribeInstanceIds operation to query the IDs of all instances. | ddoscoo-cn-i7m27nf3**** |
All Alibaba Cloud API operations must include common request parameters. For more information about common request parameters, see Common parameters.
For more information about sample requests, see the "Examples" section of this topic.
Response parameters
Examples
Sample success responses
JSON
format
{
"TotalCount": 1,
"RequestId": "0F5B72DD-96F4-423A-B12B-A5151DD746B8",
"WebRules": [
{
"Domain": "example.com",
"Http2HttpsEnable": true,
"SslProtocols": "tls1.1",
"PunishReason": 1,
"CcTemplate": "default",
"CcEnabled": true,
"SslCiphers": "default",
"Ssl13Enabled": false,
"CcRuleEnabled": false,
"OcspEnabled": false,
"PunishStatus": true,
"ProxyEnabled": true,
"CertName": "testcert",
"PolicyMode": "ip_hash",
"Cname": "kzmk7b8tt351****.aliyunddos1014****",
"Http2Enable": true,
"Https2HttpEnable": true,
"ProxyTypes": [
{
"ProxyType": "https",
"ProxyPorts": [
"443"
]
}
],
"RealServers": [
{
"RsType": 0,
"RealServer": "192.0.XX.XX"
}
],
"WhiteList": [
"192.168.XX.XX"
],
"BlackList": [
"192.0.XX.XX"
],
"CustomCiphers": [
"ECDHE-ECDSA-AES128-GCM-SHA256"
],
"GmCert": {
"CertId": "725****",
"GmEnable": 1,
"GmOnly": 1
}
}
]
}
Error codes
For a list of error codes, visit the Service error codes.