Edge Acceleration

Site Acceleration
- Overview
- Access Control
  - Token authentication
    - Token Authentication
    - Authentication Method A
    - Authentication Method B
    - Authentication Method C
    - Authentication Method D
    - Authentication Method V
- Smart Acceleration
- Cache configuration
  - Overview
  - EdgeOne caching rules introduction
    - Content Cache Rules
    - Cache Key Introduction
    - Vary Feature
  - Cache Configuration
    - Custom Cache Key
    - Node Cache TTL
    - Status Code Cache TTL
    - Browser Cache TTL
    - Offline Caching
    - Cache Prefresh
  - Clear and Preheat Cach
    - Cache Purge
    - URL Pre-Warming
    - Prefetch M3U8
  - How to improve the Cache Hit Rate of EdgeOne
- File Optimization
  - Content Compression
  - Smart Compression
- Network Optimization
  - HTTP/2
  - HTTP/3(QUIC)
    - Overview
    - Enable HTTP/3
    - QUIC SDK
      - SDK Overview
      - SDK Download and Integration
      - Sample Code
        Android
        iOS
      - API Documentation
        Android
        iOS
  - IPv6 Access
  - Maximum Upload Size
  - WebSocket
  - Client IP Geolocation Header
  - Client IP Geographical Location
  - gRPC
  - Network Error Logging
- URL Rewrite
  - Access URL Redirection
  - Origin-Pull URL Rewrite
- Modifying Header
  - Modifying HTTP Response Headers
  - Modifying HTTP Request Headers
- Modify response content
  - HTTP Response
  - Custom Error Page
- Rules Engine
  - Overview
  - Rule Management
  - variables
  - Supported Matching Types and Actions
- Image and video processing
  - Audio and Video Pre-pulling
  - Just-in-Time Image Processing
  - Video Just-In-Time Processing
  - VOD Media Origin
- Speed limit for single connection download
- Request and Response Actions
  - HTTP Response
  - Processing order
  - Default HTTP Headers of Origin-Pull Requests
  - Default HTTP Response Headers
  - HTTP Restrictions
- Media Services
  - Audio and Video Pre-pulling
  - Just-in-Time Image Processing
  - Just-in-Time Media Processing
  - VOD Media Origin
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
  - Obtaining Real TCP Client IPs via TOA
  - Obtaining Real Client IPs Through Protocol V1/V2
    - Overview
    - Method 1: Obtaining Real Client IPs Through Nginx
    - Method 2: Parsing Real Client IPs on Application Server
    - Format of Real Client IPs Obtained Through Proxy Protocol V1/V2
  - Transmitting Client Real IP via SPP Protocol
Domain name service and origin server configuration
- Domain Name Services
  - Overview
  - DNS resolution for managed domains
    - Modifying DNS Servers
    - Configuring DNS Records
    - Batch Importing DNS Records
    - Advanced DNS Configuration
  - Access accelerated domains
    - Adding A Domain Name for Acceleration
    - Ownership Verification
    - Modifying CNAME Records
    - Verify Business Access
  - Traffic scheduling
    - Traffic Scheduling Management
- HTTPS Certificate
  - Overview
  - Edge HTTPS Certificate
    - Overview
    - Deploying/Updating SSL Certificate for A Domain Name
    - Configuring A Free Certificate for A Domain Name
    - Using Keyless Certificate
  - Edge mTLS Authentication
  - Origin Certificate Validation
  - HTTPS configuration
    - Forced HTTPS Access
    - Enabling HSTS
    - SSL/TLS security configuration
      - Configuring SSL/TLS Security
      - TLS Versions and Cipher Suites
    - Enabling OCSP Stapling
  - Related References
    - Using OpenSSL to Generate Self-Signed Certificates
    - Certificate Format Requirements
    - The Difference Between one-way authentication and Mutual authentication
- Origin Configuration
  - Load Balancing
    - Overview
    - Quickly Create Load Balancers
    - Health Check Policies
    - Viewing the Health Status of Origin Server
    - Related References
      - Load Balancing-Related Concepts
      - Introduction to Request Retry Strategy
  - Origin Group Configuration
  - Origin configuration
    - Origin-Pull Timeout
    - Configuring Origin-Pull HTTPS
    - Host Header Rewrite
    - Controlling Origin-pull Requests
    - Redirect Following During Origin-Pull
    - HTTP/2 Origin-Pull
    - Range GETs
    - Modify Origin
    - Origin-pull Rate Limiting Policy
  - Origin Protection(Obtaining/Updating Origin IP Address Range)
  - Related References
    - ld Version Origin Group Compatible Related Issues

Origin Group Configuration

Overview
An origin site group is a type of origin site management unit provided by EdgeOne. You can aggregate multiple business origin sites (IPs, domain names, or COS) into a logical group and reference it uniformly in scenarios such as accelerated domain names, rule engines, and Layer-4 proxies.
Compared to configuring origin sites individually for each feature, origin groups address the following pain points:
Batch management: When an origin site changes, you only need to update it once in the origin group. All features referencing that group then take effect automatically, eliminating the need for repeated configuration.
Unified reference: Accelerated domain names, rule engines, Layer-4 proxies, and other services can share the same origin configuration, reducing maintenance costs.
Traffic distribution: It supports configuring weights for multiple origin sites within a group, enabling proportional allocation of origin-pull traffic.
The origin group configured here can be referenced in features such as Add Accelerated Domain and Layer-4 Proxy.
Use Limits
A single origin group supports a maximum of 20 origin sites.
The origin group type (HTTP Dedicated / Universal) cannot be modified after creation. Please confirm your selection when creating a new group.
If a weight is set for an origin in the origin group, weights must be set for all origins simultaneously. Weights can be integers between 0 and 100. If no weight is set, no weights should be configured for any origin.
Create Origin Group
1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the site details page, click origin configuration > origin group.
3. Click Create origin group.
4. On the Create Origin Group page, enter the origin group name and select the origin type. The specific type descriptions are as follows:
HTTP Dedicated: Supports adding IP/domain name origins and object storage origins, and can only be used for site acceleration-related services (e.g., Domain Name Service and rule engine - Modify origin).
Universal: Only supports adding IP/domain name as origin, does not support adding object storage origin, and can be used for site acceleration services (such as Domain Name Service and rule engine) and L4 proxy.
﻿
5. Click the Add Origin button to configure the origin. The supported origin types are as follows, with up to 20 origins supported.
Object storage origin: Tencent Cloud COS or other object storage buckets compatible with AWS S3.
IP/domain name origin: Supports IPv4 addresses, IPv6 addresses, and domain names as origins.
Note:
Explanation of weight-related configurations in the origin group:
1. If a weight is set for an origin in the origin group, all origins in the group must also set corresponding weights,Weights can be integers between 0 and 100.If you do not set a weight, all origins in the origin group should not set weights at the same time.
2. 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 Smart Acceleration
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 Smart Acceleration.
Origin-pull by weight ratio.
Do not configure weights for multiple origin servers in the origin server group, enable Smart Acceleration.
Origin-pull from the optimal origin server selected by Smart Acceleration.
Do not configure weights for multiple origin servers in the origin server group, do not enable Smart Acceleration.
Poll each origin site in the origin site group and perform origin-pull in equal proportion.
3. After weights are configured in the origin group, if an origin is blocked due to an exception, the weights will be redistributed among the remaining normal origins. If all origins become abnormal, the system will use round-robin to select an origin for traffic forwarding, and the weights will not take effect in this case.
﻿
6. Click Create to complete the origin group creation.
Origin Group Operation Mechanism
Origin Site Exception Blocking
By default, EdgeOne has an origin exception blocking mechanism. If origin requests fail more than five times within one minute, the abnormal origin will be blocked for ten minutes. When all origins are blocked, the first origin is selected by default for traffic forwarding.
Origin Retry Policy
Origins within an origin group are primarily used for traffic distribution, not for disaster recovery. By default, the origin group does not retry when origin requests fail. If origin retry is required, you can use the Load Balancer or Origin Site Failover feature.
References
Add Accelerated Domain: Learn how to reference an origin group in an accelerated domain.
Layer-4 Proxy: Learn how to reference an origin group in a Layer-4 proxy.
Load Balancer: Learn about capabilities related to origin retry and traffic scheduling.
﻿
﻿

Overview
Use Limits
Create Origin Group
Origin Group Operation Mechanism
- Origin Site Exception Blocking
- Origin Retry Policy
References

Scenario	Activation Logic
Configure weights for multiple origin servers in the origin server group and enable Smart Acceleration	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 Smart Acceleration.	Origin-pull by weight ratio.
Do not configure weights for multiple origin servers in the origin server group, enable Smart Acceleration.	Origin-pull from the optimal origin server selected by Smart Acceleration.
Do not configure weights for multiple origin servers in the origin server group, do not enable Smart Acceleration.	Poll each origin site in the origin site group and perform origin-pull in equal proportion.