tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
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
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Origin Configuration FAQs

PDF
Focus Mode
Font Size
Last updated: 2025-09-01 14:50:48

How to Fill in the Weight in the Origin Server Group?

When a weight is set for an origin server in the origin server group, all other origin servers must also have weights set. The weight can be an integer from 0 to 100. It is not supported to set weights for only some origin servers.

How Does It Work When an Origin Server in the Origin Server Group Has a Weight of 0?

When you set the weight of an origin server in the origin server group to 0, no traffic will be directed to that origin server. EO will route traffic back to other origin servers based on their weighted proportion out of 100.

How Does the Back-to-Origin Logic Work When Different Weights Are Configured for Multiple Origin Servers in the Origin Server Group and Intelligent Acceleration Is Enabled for the Corresponding Domain Name?

When using the combination of Smart Acceleration and origin server group weights, the following logic will apply:
Scenario
Activation Logic
Configure Weights for Multiple Origin Servers in the Origin Server Group and Enable Intelligent Acceleration for the Corresponding Domain Name
Prioritize selecting the origin server based on weight, then Smart Acceleration will optimize the return link.
Configure Weights for Multiple Origin Servers in the Origin Server Group without Enabling Intelligent Acceleration for the Corresponding Domain Name
Origin-pull by weight ratio.
Multiple origin servers in the origin server group without configuring weights, enable intelligent acceleration for the corresponding domain name
Origin-pull from the optimal origin server selected by Smart Acceleration.
Multiple origin servers in the origin server group without configuring weights, do not enable intelligent acceleration for the corresponding domain name
Poll each origin server in the origin server group, proportional origin return.

What is the impact on existing connections when changing the origin server group configuration?

When you adjust the weight of an origin server in the origin server group from a value greater than 0 to 0 or directly delete an origin server, existing established return connections will not be affected. New connections will not be forwarded to the origin server with a weight of 0 or the deleted origin server.

What are the IP range restrictions when using IP as an origin address?

IPv4 address: 0.0.0.0/8, 9.0.0.0/8, 10.0.0.0/8, 11.0.0.0/8, 30.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 127.0.0.0/8, 255.255.255.255
IPv6 address: fe80::/10, fc00::/7, ::1, ::
The above subnet ranges are not allowed to be used as EdgeOne origin IPs. If you have any questions, please contact us.

How to Configure Origin SNI

The origin SNI is set to be the same as the current origin Host by default and cannot be modified in the console.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback