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
DocumentationTencent Cloud EdgeOneSite AccelerationCache ConfigurationCache ConfigurationStatus Code Cache TTL
Status Code Cache TTL
Last updated: 2024-08-26 16:23:26
Function Introduction
When EdgeOne retrieves resources from the origin, if the origin successfully responds with the resources, EdgeOne will respond to the client request and cache it in EdgeOne for direct response next time. If the origin responds with an exception status code such as 4xx or 5xx, EdgeOne cannot obtain the resources, and the next request will still trigger a follow origin, which may put significant pressure on the origin. By configuring the status code cache TTL, EdgeOne can directly respond with the exception status code within the cache time, instead of triggering a follow origin for all requests, which can mitigate the pressure on the origin and improve the response speed.
Currently, the following status codes can be configured:
4xx: 400, 401, 403, 404, 405, 407, 414.
5xx: 500, 501, 502, 503, 504, 509, 514.
Note：
EdgeOne caches the 404 status code by default for 10 seconds.
The prerequisite for the status code cache to take effect is that the resource can be cached in the node according to the node cache TTL configuration. If the resource is not cached in the node, the status code cache will not be triggered.
Directions
Scenario 1: Configure status code cache TTL for all domain names of a site
If you need to configure the status code cache TTL for the whole connected site, or as a fallback configuration for the site level, please refer to the following steps:
1. Log in to the EdgeOne console, click Site List in the left sidebar, and then click the site you want to configure in the site list.
2. On the site details page, click Site Acceleration to enter the global configuration page. Then click the Rule Engine tab.
3. On the rule engine page, click Create rule and select Add blank rule.
4. On the rule editing page, select the matching type as All.
5. Click the operation, and in the pop-up operation list, select the operation as status code cache, and configure the corresponding cache status code and cache time.
6. Click save and publish to complete the rule configuration.
Scenario 2: Configure status code cache TTL for specified domain names, paths, or file extensions
If you need to configure different status code cache TTL for different domain names, paths, or file extensions, for example, configure the status code cache TTL for the www.example.com domain under the example.com site, please refer to the following steps:
1. Log in to the EdgeOne console, click Site List in the left sidebar, and then click the site you want to configure in the site list.
2. On the site details page, click Site Acceleration to enter the global configuration page. Then click the Rule Engine tab.
3. On the rule engine page, click Create rule and select Add blank rule.
4. On the rule editing page, select Host as the matching type and configure it as
www.example.com.5. Click the operation, and in the pop-up operation list, select the operation as status code cache, and configure the corresponding cache status code and cache time.
6. Click save and publish to complete the rule configuration.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No