Feature Overview
When a page access error occurs, the client shows a default page, such as 404 Not Found. The default error page is not visually appealing in most cases, resulting in a poor user experience.
To improve user experience, you can configure edge POPs so that requests are redirected to custom error pages when errors occur.
Before You Begin
You have added a service domain name. If you have not added it, see Adding a Service Domain Name.
Cautions
• This feature is only available if the client supports 302 redirects.
• You can customize error pages for common HTTP status codes such as 400, 403, 404, 405, 414, 416, 500, 501, 502, 503, and 504.
• The format of error pages is http(s)://example.ctyun.cn/error404.html. Enter a complete URL that contains http or https.
Procedure
Currently, this feature cannot be configured on your own. To configure this feature, submit a ticket to the eSurfing Cloud’s technical support team.
When submitting a ticket, provide the following information:
Parameter | Description |
Status Code | Example: 404. Submit a supported status code. |
URL | Example: http://example.ctyun.cn/error404.html. |