Pricing
PURCHASE OPTIONS​
PRICING GUIDANCE​
🎉 EdgeOne Free Plan Launches! The World's First Free CDN with China Access – Join the Event to Unlock Multiple Plans!

EdgeOne Q2 Product Updates: Major Upgrades to Rules Engine and Origin Protection

EdgeOne-Product Team
10 min read
Jul 29, 2025

EdgeOne remains committed to listening to user feedback, continuously iterating product upgrades, and exploring advanced technology directions. In this update, we will focus on the significant enhancements made this quarter in the Edge Acceleration module, specifically the Rules Engine and Origin Protection.

Rules Engine

Enhanced Flexibility for Diverse Business Scenarios

To address the diverse needs of various business scenarios, users require a Rules Engine with more flexible matching conditions. For example, in the e-commerce sector, traffic surges during promotional events may cause certain pages to return specific status codes (such as 404 or 410) due to stock depletion. The Rules Engine can automatically adjust caching policies based on these status codes, reducing backend request pressure and preventing resource waste caused by invalid traffic. Additionally, it allows flexible configuration of cache duration and scope based on response headers (e.g., Cache-Control, Set-Cookie), ensuring users receive timely and accurate page content, thereby improving overall user experience.

Rule Engine Standardization Enhancements: Flexibly Catering to More User Scenarios

To improve standardization and flexibility, the rule engine now supports:

1. Response attribute matching conditions in the rule engine. Phase one supports only "HTTP response," "modification of HTTP node response headers," and "browser cache TTL" operations, with additional operations planned for future releases;

2. Expanded matching conditions supported for the rule engine’s "Node Cache TTL" operation;

3. Vary header feature within the rule engine;

4. Cookie matching conditions in the rule engine;

5. Addition of "regex non-match" support and expansion of the scope of "regex match" conditions;

6. Regex-based replacements in the rule engine’s "origin URL rewriting" operation.

Rule Engine

Origin Protection

Firewall Rule Limits: Strict Change Management Policies

Enterprises need CDN provider IP ranges for origin firewall rules, but face limitations on rule quantities and strict change management policies. Frequent IP changes create operational burdens.

Origin Protection Upgrade: Reduced IP Ranges and Lower Update Frequency

For accelerated domains and Layer 4 proxy instances, EdgeOne provides origin IP ranges for configuring origin firewall rules, allowing only traffic from fixed IPs to reach the origin and ensuring origin protection. This update reduces the number of IP ranges from more than 300 to less than 200; decreases the change frequency from once a week under normal circumstances to once every 3-6 months; extends support to Personal and Basic plans to meet the origin protection needs of a broader range of developers and small-to-medium enterprises; and introduces API capabilities to support integration with automated Ops.

Origin Protection

EdgeOne will continue to listen attentively to user feedback, persistently iterate product upgrades, and provide more stable, secure, and efficient services to safeguard your business.