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
- Related References
- Legacy Console Relevant Documentation
- Security 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
Processing order
Last updated: 2024-05-28 14:03:42
This article introduces the processing order of various module rules configured in the platform after the client initiates a request to EdgeOne, helping users understand the effective order and impact of the rules to ensure that the configured rules work as expected.
Processing order
After the user initiates a request, the request will be processed in the above order. For example, if the user configures the modification of HTTP headers in both the rule engine and the Edge functions, the final result will be based on the processing of the Edge functions since they are processed later.
1. Multiple rules may be triggered in the security service module, and the relevant processing order is as follows:
The DDoS protection request processing order only applies to users who have purchased the exclusive DDoS protection with L4 proxy. For details, please refer to the DDoS protection overview.
The Web protection module contains the bot management module. For the request processing order within the Web protection module, please refer to the Web Protection request processing order. For the rule application order within the bot management module, please refer to the bot management overview.
If a request triggers a security policy in the EdgeOne security protection module, and the action is interception, discard and blacklist, or IP blocking, the request will be rejected.
2. The rule priority in the rule engine is higher than the global site setting rules, and the rule application order in the rule engine is that the lower rules have higher priority. For details, please refer to the rule engine overview.
3. When a request triggers an Edge function rule, the request will be processed by the Edge functions. Edge functions can access third-party services, EdgeOne cache content, or return to the client's origin through sub-requests, or directly respond to client requests.
4. When requests to the EdgeOne node Cache, if the current node does not have Cache, it will continue to origin-pull. If the node hits the Cache, it will not Trigger the subsequent origin-pull rules and directly Return the corresponding resources to the user.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No