Edge Acceleration

Site Acceleration
- Overview
- Quickly Import and Export Site Configuration
- Access Control
  - Token Authentication
- Smart Acceleration
- File Optimization
  - 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
- URL Rewrite
  - Access URL Redirection
  - Origin-Pull URL Rewrite
- Modifying Header
  - Modifying HTTP Response Headers
  - Modifying HTTP Request Headers
- Custom Error Page
- Request and Response Actions
  - Processing order
  - Default HTTP Headers of Origin-Pull Requests
  - Default HTTP Response Headers
- 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
Edge DNS
- Hosting DNS Records
  - Modifying DNS Servers
  - Configuring DNS Records
  - Advanced DNS Configuration
- Domain Connection
  - Adding A Domain Name for Acceleration
  - Ownership Verification
  - Modifying CNAME Records
- Domain alias
  - Overview
  - Configuration Guide
  - Batch Connecting SaaS Domain Names
  - Configuring Alias Domain Names for Disaster Recovery
- Traffic Scheduling
  - Traffic Scheduling Management
- Origin Configuration
  - Origin-pull configuration
    - Configuring Origin-Pull HTTPS
    - Host Header Rewrite
    - Controlling Origin-pull Requests
    - Redirect Following During Origin-Pull
    - HTTP/2 Origin-Pull
    - Range GETs
  - 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
  - Related References
    - ld Version Origin Group Compatible Related Issues
  - Collect EdgeOne origin-pull node IP
Edge Cache
- Overview
- EdgeOne Cache Rules
  - 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
- How to improve the Cache Hit Rate of EdgeOne
Rules Engine
- Overview
- Supported Matching Types and Actions
- Rule Management
- variables

Adding A Domain Name for Acceleration

This document describes how to connect your domain name to EdgeOne and enable domain acceleration.
Note:
Chinese, Korean, and Japanese domain names are not currently supported for Punycode conversion.
After a domain name is created, EdgeOne will assign a CNAME address to it. You need to complete the CNAME configuration to enable secure acceleration for the domain name. For configuration methods, refer to Modifying CNAME Records.
Prerequisites
1. You have connected the site (such as example.com) to EdgeOne. If you want to accelerate domain names in Chinese mainland AZs or global AZs, please complete ICP filing first.
2. Your site is hosted on an accessible service, such as Cloud Virtual Machine (CVM) or Cloud Object Storage (COS). For example, you have built a cross-border e-commerce site based on Tencent Cloud CVM, and the current server IP address is: 10.1.1.1.
3. If the site is connected via CNAME, you must verify ownership of the domain name. If the site is connected via NS, you must modify DNS server addresses first.
Scenario 1: Quickly Adding a Domain Name
If your domain name does not require complex configuration, you can click  Quick add  to add a domain name and quickly connect to EdgeOne.
1. Log in to the EdgeOne console, select the  site  to configure from the site list and enter the site management submenu.
2. On the left navigation bar, click  Domain Name Service  >  Domain Management  to enter the domain name management page.
3. Click  Quick add  to add a new domain name. Fill in the domain name configuration information by referring to Description of Domain Name Configuration Items, and then click  Save  to apply the domain name configuration .
﻿
Scenario 2: Adding a Domain Name and Completing Basic Configuration
If you need to fully configure the domain name's basic information, such as the origin-pull protocol and origin-pull port, it is recommended to use Add domain name. The steps for adding a domain name will vary based on the connection mode you choose.
Connecting via NS
Connecting via CNAME
DNSPod Managed Access
1. Log in to the EdgeOne console, select the  site  to configure from the site list and enter the site management submenu.
2. On the left navigation bar, click  Domain Name Service  >  Domain Management  to enter the domain name management page.
3. Click  Add domain name . Fill in the domain name configuration information by referring to Description of Domain Name Configuration Items, and then click  Next.
4. When a domain name is added, EdgeOne provides recommended configurations based on common business scenarios to ensure your business runs more securely and smoothly. You can choose the recommended configuration based on your business scenarios, and the corresponding configuration will be displayed as a rule in the rule engine module. You can click  Complete  to apply the recommended configuration and create an accelerated domain name, or you can directly click  Skip  to create an accelerated domain name without applying any recommended configuration.
5. In the NS access mode, EdgeOne will automatically add a CNAME address directing to EdgeOne based on your domain name in the background. You can click One-click Add to immediately enable acceleration. If you need to complete other domain name configurations, you can also click Add Later and refer to Modify CNAME Records for the configuration.
1. Log in to the EdgeOne console, select the  site  to configure from the site list and enter the site management submenu.
2. On the left navigation bar, click  Domain Name Service  >  Domain Management  to enter the domain name management page.
3. Click  Add domain name . Fill in the domain name configuration information by referring to Description of Domain Name Configuration Items, and then click  Next .
4. When a domain name is added, EdgeOne provides recommended configurations based on common business scenarios to ensure your business runs more securely and smoothly. You can choose the recommended configuration based on your business scenarios, and the corresponding configuration will be displayed as a rule in the rule engine module. You can click  Next  to apply the recommended configuration and create an accelerated domain name, or you can directly click  Skip  to create an accelerated domain name without applying any recommended configuration.
5. In CNAME access mode, EdgeOne will assign a CNAME address to the domain name. You need to complete the CNAME configuration to enable secure acceleration for the domain name. For configuration methods, refer to Modifying CNAME Records. After completing the configuration, click  Finish .
1. Log in to the EdgeOne console, select the  site  to configure from the site list and enter the site management submenu.
2. On the left navigation bar, click  Domain Name Service  >  Domain Management  to enter the domain name management page.
3. Click  Add domain name . Fill in the domain name configuration information by referring to Domain Name Configuration Item Description, and then click  Next .
4. When a domain name is added, EdgeOne provides recommended configurations based on common business scenarios to ensure your business runs more securely and smoothly. You can choose the recommended configuration based on your business scenarios, and the corresponding configuration will be displayed as a rule in the rule engine module. You can click  Next  to apply the recommended configuration and create an accelerated domain name, or you can directly click  Skip  to create an accelerated domain name without applying any recommended configuration.
5. In DNSPod managed access mode, EdgeOne will assign a CNAME address to the domain name. You can use  One-click Add  to make EdgeOne automatically complete the CNAME configuration for the domain name. If you need to complete other domain name configurations, you can also click  Add Later  and refer to Modifying CNAME Records for configuration.
References
Description of Domain Name Configuration Items
Configuration Item
Description
Domain name
A domain name provided for client access. Enter the host record value corresponding to the domain name. Wildcard domain name access is supported. If you need to access the primary domain name, enter @.
For example: If you need to accelerate the website  www.example.com , enter  www  here.
Origin settings
The origin server is the final resource address accessed when the client initiates a request. You can choose from IP/Domain name, COS origin server, and Origin Group:
 IP/Domain name: Used to connect a single origin server. You can enter a single IP address or a single domain name as the origin server.
 COS origin server: Used to add Tencent Cloud COS and an AWS S3-compatible COS bucket as the origin server. If the bucket has public read-write access, you can also access it directly using the IP/Domain name origin server type.
﻿Origin Group: If the origin server has multiple IP addresses, you can add them by configuring an origin server group.
﻿Load balancing:  Origin server latency and health status are actively detected, and intelligent traffic scheduling policies are configured to provide more secure and efficient traffic distribution services.
﻿VOD: For buckets authorized in VOD, the distribution scope can be set to all files within the application or files in a specific bucket.
For example: There is a cross-border e-commerce website built using Tencent CVM. The server IP address is  10.1.1.1 . When configuring the origin server, select IP/Domain name for Origin settings and enter the server address.
 Note:
1. We recommend that you configure your origin server in the same region as the acceleration region. For example, if the acceleration region is a Chinese mainland availability zone, set the origin server to be within the Chinese mainland for better origin-pull performance. If the origin server is in a global availability zone (excluding the Chinese mainland) and requires cross-border access, the origin-pull effect may not be guaranteed. To accelerate access for Chinese mainland users with the origin server in a global availability zone (excluding the Chinese mainland), refer toCross-regional Secure Acceleration (Oversea Sites).
2. If your acceleration region is a global availability zone, you can add corresponding rules in the rule engine. Set the matching condition to the client's geo location and choose to modify the origin server, directing requests to different origin servers based on the regions to ensure the origin-pull effect.
3. If your origin server type is IP/Domain name, the default origin host is the accelerated domain name. If you need to specify a domain name for the origin host, refer to Host Header Rewrite. If your origin server is a COS origin server, the default origin host is the COS origin server domain name.
IPv6 access
Choose whether to enable IPv6 access. Refer to IPv6 Access. The default is to follow site configuration.
Origin Protocol
Select the protocol supported by your origin server. The default is to follow the protocol. Options:
 Follow protocol: The origin-pull protocol is the same as the user request protocol.
 HTTP : Use the HTTP protocol for origin-pull.
 HTTPS:  Use the HTTPS protocol for origin-pull.
Origin Port
Specify the port used for origin-pull. Ensure that the port specified on your origin server is accessible. By default, HTTP origin-pull uses port 80, and HTTPS origin-pull uses port 443.
Verifying Domain Name Acceleration
The verification procedure varies based on the access mode you have selected.
NS Access
CNAME Access
DNSPod Managed Access
In NS access mode, when the client accesses the accelerated domain, EdgeOne automatically schedule the access to the nearest edge node. You can check whether the IP address of the assigned edge node is on EdgeOne to verify whether the site has been added to EdgeOne.
You can obtain the IP address of the assigned edge node as instructed below.
Windows
Mac/Linux
1. Open the command prompt and run the nslookup -qt=A www.example.com command. Then, check the IP address of the domain obtained by the A record resolution.
﻿
2. On the IP Location Query page of the EdgeOne console, paste the IP address in the IP field and click Search to check whether the IP address is on EdgeOne. If yes, DNS of the accelerated domain has been switched to EdgeOne.
﻿
1. Open the terminal and run the dig www.example.com command. Then, check the IP address of the domain obtained by the A record resolution.
﻿
2. On the IP Location Query page of the EdgeOne console, paste the IP address in the IP field and click Search to check whether the IP address is on EdgeOne. If yes, DNS of the accelerated domain has been switched to EdgeOne.
﻿
After you complete the CNAME configuration, EdgeOne automatically detects whether the CNAME configuration has taken effect. In the domain list, if the Status of the accelerated domain is Activated, the domain is correctly configured and accelerated.
﻿
If you have correctly configured the CNAME record, but the status is not Activated, this may be caused by the CNAME resolution latency of the DNS provider. In this case, you can manually verify the connection as instructed below.
Windows
Mac/Linux
Open the command prompt and run the nslookup -qt=cname www.example.com command. Then, check the CNAME information of the domain. If the CNAME information is the same as that provided by EdgeOne, DNS of the accelerated domain has been switched to EdgeOne.
﻿
Open the terminal and run the dig www.example.com command. Then, check the CNAME information of the domain. If the CNAME information is the same as that provided by EdgeOne, DNS of the accelerated domain has been switched to EdgeOne.
﻿
After you complete the CNAME configuration, EdgeOne automatically detects whether the CNAME configuration has taken effect. In the domain list, if the Status of the accelerated domain is Activated, the domain is correctly configured and accelerated.
﻿
If you have correctly configured the CNAME record, but the status is not Activated, this may be caused by the CNAME resolution latency of the DNS provider. In this case, you can manually verify the connection as instructed below.
Windows
Mac/Linux
Open the command prompt and run the nslookup -qt=cname www.example.com command. Then, check the CNAME information of the domain. If the CNAME information is the same as that provided by EdgeOne, DNS of the accelerated domain has been switched to EdgeOne.
﻿
Open the terminal and run the dig www.example.com command. Then, check the CNAME information of the domain. If the CNAME information is the same as that provided by EdgeOne, DNS of the accelerated domain has been switched to EdgeOne.
﻿
﻿

Prerequisites
Scenario 1: Quickly Adding a Domain Name
Scenario 2: Adding a Domain Name and Completing Basic Configuration
References
- Description of Domain Name Configuration Items
- Verifying Domain Name Acceleration

Configuration Item	Description
Domain name	A domain name provided for client access. Enter the host record value corresponding to the domain name. Wildcard domain name access is supported. If you need to access the primary domain name, enter @. For example: If you need to accelerate the website `www.example.com` , enter `www` here.
Origin settings	The origin server is the final resource address accessed when the client initiates a request. You can choose from IP/Domain name, COS origin server, and Origin Group: IP/Domain name: Used to connect a single origin server. You can enter a single IP address or a single domain name as the origin server. COS origin server: Used to add Tencent Cloud COS and an AWS S3-compatible COS bucket as the origin server. If the bucket has public read-write access, you can also access it directly using the IP/Domain name origin server type. Origin Group: If the origin server has multiple IP addresses, you can add them by configuring an origin server group. Load balancing: Origin server latency and health status are actively detected, and intelligent traffic scheduling policies are configured to provide more secure and efficient traffic distribution services. VOD: For buckets authorized in VOD, the distribution scope can be set to all files within the application or files in a specific bucket. For example: There is a cross-border e-commerce website built using Tencent CVM. The server IP address is `10.1.1.1` . When configuring the origin server, select IP/Domain name for Origin settings and enter the server address. Note: 1. We recommend that you configure your origin server in the same region as the acceleration region. For example, if the acceleration region is a Chinese mainland availability zone, set the origin server to be within the Chinese mainland for better origin-pull performance. If the origin server is in a global availability zone (excluding the Chinese mainland) and requires cross-border access, the origin-pull effect may not be guaranteed. To accelerate access for Chinese mainland users with the origin server in a global availability zone (excluding the Chinese mainland), refer toCross-regional Secure Acceleration (Oversea Sites). 2. If your acceleration region is a global availability zone, you can add corresponding rules in the rule engine. Set the matching condition to the client's geo location and choose to modify the origin server, directing requests to different origin servers based on the regions to ensure the origin-pull effect. 3. If your origin server type is IP/Domain name, the default origin host is the accelerated domain name. If you need to specify a domain name for the origin host, refer to Host Header Rewrite. If your origin server is a COS origin server, the default origin host is the COS origin server domain name.
IPv6 access	Choose whether to enable IPv6 access. Refer to IPv6 Access. The default is to follow site configuration.
Origin Protocol	Select the protocol supported by your origin server. The default is to follow the protocol. Options: Follow protocol: The origin-pull protocol is the same as the user request protocol. HTTP : Use the HTTP protocol for origin-pull. HTTPS: Use the HTTPS protocol for origin-pull.
Origin Port	Specify the port used for origin-pull. Ensure that the port specified on your origin server is accessible. By default, HTTP origin-pull uses port 80, and HTTPS origin-pull uses port 443.