Resources
  • News and Announcements
    • Release Notes
    • Security Announcement
    • Announcements
  • TEO Policy
    • Privacy Policy
    • Data Processing And Security Agreement
  • Contact Us
  • Glossary
  • FAQs
    • Product Features FAQs
    • Domain Service FAQs
    • Domain Configuration FAQs
    • Site Acceleration FAQs
    • Data and Log FAQs
    • Security Protection-related Queries
    • Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
  • AI Resources and Terraform
    • EdgeOne Skill Introduction and Usage Guide
    • Overview
    • Installing and Configuring Terraform
  • General Reference
    • Configuration Syntax
      • Overview
      • Configuration Group Syntax Explanation
      • Condition
      • Variables
    • Request and response behavior
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
      • HTTP Restrictions
    • Country/region and Corresponding Codes
  • Related Agreements
    • Service Level Agreement
    • Origin Protection Enablement Conditions of Use

Overview

Configuration syntax is a standardized format based on JSON for defining, exporting, and importing site configurations.
Version management: This grammar allows you to compare configuration differences between different versions and fast rollback to earlier versions. Users can directly view change details in JSON format in the version history, or create a new version by editing JSON text to implement precise adjustment of configured settings.
Configuration import and export: Users can write or modify JSON configuration files according to this syntax to achieve rapid configuration copying between different sites, batch update configurations, or restore original configurations.

Function Module Configuration Example

Each feature module in the console has an independent syntax format. Before checking the following example, it is advisable to get familiar with the core component of configuration syntax.
To view the complete configuration parameter description, please refer to Configuration Group Syntax Explanation.
Syntax Examples
{
"FormatVersion": "1.0", // Configuration format version
"ZoneConfig": { //Site-level configuration, containing all configuration items for "site acceleration"
......
},
"Rules": [ //Hierarchical configuration containing all rules in the rule engine
{
"RuleName": "test",
"Branches": [
{
"Condition": "${http.request.host} in ['example.com']",
"Actions": [
...... //rule operation list
]
}
]
}
],
"WebSecurity": { // Web security configuration root object
"ZoneDefaultPolicy": { // Default (global) policy
......
},
"HostPolicy": [ // Domain-level security policy
......
],
"Templates": [ // Protection Policy Template
......
]
}
}