Tencent Cloud EdgeOne
- Release Notes and Announcements
- Security Announcement
- Announcements
- Product Introduction
- Purchase Guide
- Billing Items
- Basic Service Fees
- Value-added Service Fees
- Instructions for overdue and refunds
- Getting Started
- Domain Service&Origin Configuration
- Domain Service
- Hosting DNS Records
- Domain Connection
- Traffic Scheduling
- HTTPS Certificate
- HTTPS Configuration
- SSL/TLS Security Configuration
- Origin Configuration
- Load Balancing
- Related References
- Origin-pull configuration
- Related References
- Site Acceleration
- Access Control
- Cache Configuration
- EdgeOne Cache Rules
- Cache Configuration
- Clear and Preheat Cach
- File Optimization
- Network Optimization
- HTTP/3(QUIC)
- QUIC SDK
- Modifying Header
- Modify the response content
- Rule Engine
- Related References
- Request and Response Actions
- DDoS & Web Protection
- DDoS Protection
- Configuration of Exclusive DDoS protection Rules
- Related References
- Web Protection
- Rate Limiting
- Bot Management
- Related References
- Related References
- Image&Video Processing
- Edge Functions
- Runtime APIs
- Streams
- Images
- Sample Functions
- Best Practices
- L4 Proxy
- Obtaining Real Client IPs
- Obtaining Real Client IPs Through Protocol V1/V2
- Data Analysis&Log Service
- Log Service
- Real-time Logs
- Data Analysis
- Alarm Service
- Version Management
- Site and Billing Management
- Site Management
- General Policy
- Terraform
- Practical Tutorial
- Automatic Warm-up/Cache Purge
- Resource Abuse/hotlinking Protection Practical
- HTTPS Related Practices
- Acceleration Optimization
- Scheduling Traffic
- Origin-pull Based On User IP/geolocation
- APK Dynamic Packaging
- Data Analysis and Alerting
- API Documentation
- Making API Requests
- Site APIs
- Acceleration Domain Management APIs
- Site Acceleration Configuration APIs
- Edge Function APIs
- Alias Domain APIs
- Security Configuration APIs
- Layer 4 Application Proxy APIs
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- DNS Record APIs
- Content Identifier APIs
- Old Version APIs
- Version Management APIs
- Common Guidelines
- FAQs
- Troubleshooting
- Tool Guide
- Speed Test Tools
- Diagnostic Tool
- Agreements
Custom Error Page
Last updated: 2024-08-26 11:10:08
Overview
EdgeOne provides support to redirect to a specified custom page and return a 302 status code when the origin server responds with specific error statuses. This helps your site inform users of the current website status by the customized error page, avoiding uncertainty regarding the specific cause and resolution when a request error occurs.
Note
This feature is the redirection of origin-pull error status. It does not support redirection of status codes generated by access control policies such as token authentication or web protection rules.
Directions
For instance, your self-built e-commerce service website provides online payment capability through
shop.example.com. During peak user traffic, the original server could potentially become overloaded, responding with a 503 status code. In order to avoid losing users, I hope to customize an error page https://www.example.com/error.html to guide users to other e-commerce platforms. You can follow the steps:1. Log in to the TencentCloud EdgeOne console and click Site List in the left sidebar.In the site list, click the target Site.
2. On the site details page, click Site Acceleration to enter the global site configuration page, then click the Rule Engine tab.
3. On the rule engine management page, click Create rule and select Add blank rule.
4. On the rule editing page, select the matching type as HOST equal to
shop.example.com.5. Click Action, and select Custom Error Page in the pop-up action list.
6. To configure the custom error page, select the Status code as 503 and enter
https://www.example.com/error.html for the Page URL. The relevant configuration items are described as follows:Configuration Item | Description |
Status code | Specifies the error status code returned by the origin: 4XX:400, 403, 404, 405, 414, 416, 451 5XX:500, 501, 502, 503, 504 |
Page URL | Designate the error page address, for instance: https://www.example.com/custom-page.html |
7. The complete rule configuration is as shown below. Click Save and publish, the rule configuration will be completed.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No