Creates a custom error page, which is displayed when a request is blocked by Web Application Firewall (WAF). You can configure the HTML content, page type, and description, and submit the Base64-encoded page content.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| esa:CreatePage | create | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| Name | string | Yes | The name of the custom error page. | example |
| Description | string | No | The description of the page. | a custom deny page |
| ContentType | string | Yes | The Content-Type field in the HTTP header. Valid values:
| text/html |
| Content | string | No | The Base64-encoded page content. Example: "PGh0bWw+aGVsbG8gcGFnZTwvaHRtbD4=", which indicates "hello page". | PGh0bWw+aGVsbG8gcGFnZTwvaHRtbD4= |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "36af3fcc-43d0-441c-86b1-428951dc8225",
"Id": 50000001
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InvalidParameter | The specified parameter is invalid. | The specified parameter is invalid. |
| 400 | InternalException | Failed to call the service. Try again later or contact technical support. | Failed to call the service. Try again later or contact technical support. |
| 403 | %s.NotSupport | The specified resource type %s is not supported. | The specified resource type is not supported. To use this type of resource, please contact us. |
| 403 | %s.OverQuota | The quantity of %s exceeds the quota. | The amount of this resource exceeds the quota. If you need to apply for more quota, please contact us. |
| 403 | %s.WrongValueMatched | The value of specified parameter %s can not pass the matching check. | The value of the specified parameter can not pass the matching check. If you determine that you need to use this parameter value, please contact us. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-09-25 | The Error code has changed | View Change Details |
| 2024-09-18 | The Error code has changed | View Change Details |