Prefetches cache.
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:PreloadCaches | create | *Site acs:esa:{#regionId}:{#accountId}:site/{#SiteId} |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| SiteId | long | No | The website ID. You can call the ListSites operation to obtain the ID. | 123456789**** |
| Content | array | No | The files to be prefetched. | |
| string | No | The single file to be prefetched. | http://a.com/1.jpg?b=1 | |
| Headers | object | No | By default, prefetch requests include the Accept-Encoding:gzip header. If you want a prefetch request to include other headers or implement multi-replica prefetch, you can specify a custom prefetch header by configuring the Headers parameter. | |
| string | No | The request header. | Accept-Encoding:gzip |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "9732E117-8A37-49FD-A36F-ABBB87556CA7",
"TaskId": 16401427840
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | MissingTimeParameter | The StartTime and EndTime must be both specified. | Please provide both a start time and an end time. |
| 400 | InvalidEndTime.Mismatch | The specified EndTime is earlier than the StartTime. | The end time you entered is earlier than the start time. Please check and try again. |
| 400 | DomainNameOverLimit | A maximum of 500 domains are supported for each request. | Only 500 domain names are supported at a time. Please reduce the number of domain names to request again. |
| 400 | InvalidTime | The query time cannot exceed the last 3 days. | The query time cannot exceed the last 3 days. |
| 400 | MissingParameter.ObjectType | The ObjectType parameter is required if DomainName or ObjectType is specified. | Specify the ObjectType parameter. |
| 400 | InvalidStationParameter | The specified Station is invalid. | The specified node parameter is invalid. |
| 400 | TooManyRequests | Too many requests.Please try again later. | Requests are too frequent, please try again later. |
| 400 | InvalidTaskId.Malformed | The specified taskId is invalid. | The specified task ID is invalid. |
| 400 | InvalidParameters.InvalidUrls | The specified urls are invalid. | The requested URL parameter is invalid. |
| 400 | QuotaExceeded | You attempts have exceeded the daily limit. | Exceeding the same day quota limit. The number of submissions today has been exhausted. You can query the number of times a quota can be used today through the quota API. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2025-03-13 | The Error code has changed | View Change Details |
| 2024-10-15 | The Error code has changed | View Change Details |