Tencent Cloud EdgeOne

Tencent Cloud EdgeOne
Origin Configuration
Product Documentation©2013-2022 Tencent Cloud. All rights reserved.

Page 1 of 52

Tencent Cloud EdgeOne

Copyright Notice©2013-2024 Tencent Cloud. All rights reserved.
Copyright in this document is exclusively owned by Tencent Cloud. You must not reproduce, modify, copy or distributein any way, in whole or in part, the contents of this document without Tencent Cloud's the prior written consent.
Trademark Notice

All trademarks associated with Tencent Cloud and its services are owned by Tencent Cloud Computing (Beijing)
Company Limited and its affiliated companies. Trademarks of third parties referred to in this document are owned bytheir respective proprietors.
Service Statement
This document is intended to provide users with general information about Tencent Cloud's products and services
only and does not form part of Tencent Cloud's terms and conditions. Tencent Cloud's products or services are
subject to change. Specific products and services and the standards applicable to them are exclusively provided for in
Tencent Cloud's applicable terms and conditions.

©2013-2022 Tencent Cloud. All rights reserved.

Page 2 of 52

Tencent Cloud EdgeOne

Contents
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-pull configuration
Configuring Origin-Pull HTTPS
Host Header Rewrite
Controlling Origin-pull Requests
Redirect Following During Origin-Pull
HTTP/2 Origin-Pull
Range GETs
Related References
ld Version Origin Group Compatible Related Issues
VOD Origin Server Details
Collect EdgeOne origin-pull node IP©2013-2022 Tencent Cloud. All rights reserved.

Page 3 of 52

Tencent Cloud EdgeOne

Origin Configuration
Load Balancing
Overview：

Last updated 2024-05-29 10:33:37
EdgeOne Load Balancing is ideal for scenarios where high availability of origins is crucial. It supports the configurationof multi-level secondary sources for disaster recovery switching. It can proactively probe the health status of origins.
This proactive measure blocks failed origins and directs business traffic to healthy origins.
Note:
EdgeOne Load Balancing feature is in beta testing. If you want to use it, you can Contact Us.

Use Cases
Hardware failures, network failures, configuration errors, security attacks, natural disasters, human errors, and other
unforeseen circumstances, can affect the availability of the origin. For businesses that require high availability, such as
finance, gaming, audio and video, and e-commerce, even brief failures of the origin can result in significant losses.
Therefore, it is necessary to implement primary/secondary disaster recovery and health checks for the origin.
Primary/Secondary Disaster Recovery: When the primary source becomes unavailable, it is automaticallyswitched to the secondary source to ensure business continuity.
Proactively Checking origin Health Status: Preemptively disables failed origins, and redirects business traffic tohealthy origins. Prevents a situation where a significant number of legitimate service requests are still directed tomalfunctioning origins in the event of a failure.

Supported Capabilities
1. Supports the configuration of multi-level secondary sources for multi-source disaster recovery.
2. Supports the configuration of health check policies such as ICMP Ping, HTTP/HTTPS, TCP, and UDP topreemptively disable failed origins and redirect business traffic to healthy origins.
3. Provides a fallback retry policy. It retries directing the traffic to alternative healthy origins when real business traffic
requests fail.

©2013-2022 Tencent Cloud. All rights reserved.

Page 4 of 52

Tencent Cloud EdgeOne

More Information
Quickly Create Load Balancers﻿
Load Balancing-Related Concepts﻿
Health Check Policies©2013-2022 Tencent Cloud. All rights reserved.

Page 5 of 52

Tencent Cloud EdgeOne

Quickly Create Load Balancers：

Last updated 2024-05-29 10:33:37
This document guides you on how to create a Cloud Load Balancer instance.
Note:
EdgeOne Load Balancing feature is in beta testing. If you want to use it, you can Contact Us.

Sample Scenario
For example, you currently have an acceleration domain www.example.com , with three origins 1.2.3.4 ,
2.3.4.5 , and 3.4.5.6 . Under normal circumstances, both 1.2.3.4 and 2.3.4.5 are used as primary
origins. You have already configured them as the origin group named primary_origins following the Origin GroupOperation Guide. The server 3.4.5.6 is used as a standby origin in a group called backup_origins, which is only used
when the primary origins fail. In cases where a real business request fails, retries are attempted with other healthy
servers within the same group. Additionally, there is a requirement for proactive probing to actively identify and disable
unhealthy origins.

Directions
1. Log in to the Tencent Cloud EdgeOne console. In the left menu bar, click the Site List. Within this list, click the Sitethat need to be configured to go to the details page.
2. On the site details page, click Origin Settings > Load Balancing.
3. On the Load Balancing page, click Create Instance.

4. Proceed to step 1 of choosing the origin. You need to fill in the instance name, choose the instance type, and add an
origin group.
Taking this scenario as an example, add the origin group primary_origins as a priority 1 origin group, add the origingroup backup_origins as a priority 2 origin group, and click Next.

©2013-2022 Tencent Cloud. All rights reserved.

Page 6 of 52

Tencent Cloud EdgeOne

Parameter

Description

Instance
name

Limit to 1-200 characters in length. Allowed characters are a-z, A-Z, 0-9, _, -.
HTTP-specific Type: Supports adding both HTTP-specific and general origin groups. It is only

Instance
type

applicable for reference by site acceleration-related services, such as domain services and ruleengines.
General Type: Only supports adding general origin groups. It is applicable for site acceleration
services including domain services and rule engines, and reference by L4 proxy service.

Add origin
group

In the CLB instance, the smallest configuration dimension for an origin is the origin group. You
need to configure the origin into an origin group and add it here. For more details, see Origin
Group Configuration.
You can set priorities for the added origin groups. Traffic will not be directed to origins in lowerpriority origin groups if there are healthy origins in higher-priority origin groups. Up to 10 origingroups can be configured, with lower numbers indicating higher priorities.

5. Proceed to step 2 of health check policy. It supports four types of probes: ICMP Ping, HTTPS/HTTP, TCP, andUDP. Tencent Cloud EdgeOne will actively send probe requests to your origin to check its latency and health status.
You can choose the appropriate probe frequency based on the load condition of your origin. Here, choose ICMP Ping
as the probe policy. For a detailed introduction to probe policy configuration, see Introduction to Health Check Policy.
After configuration is completed, click Next.

©2013-2022 Tencent Cloud. All rights reserved.

Page 7 of 52

Tencent Cloud EdgeOne

Note:
If you do not want EdgeOne's nodes to initiate any probe requests to origins, you can choose Not Enabled. In thiscase, the Load Balancing instance will default to traffic scheduling based on the priority order of the origin groups fromstep 1. If a request to a particular origin fails 5 times within 60 seconds, the corresponding origin will be disabled for
10 minutes according to the default policy.
Using this policy will not be able to disable the origin of the failure in advance, and it will not be able toautomatically and quickly recover the traffic scheduling after the origin returns to normal. Compared withenabling active probe, using this policy may cause you to encounter more failed requests during the origin failure
period. Therefore, if you want your business to have higher availability, it is recommended that you enable active
probe.
6. Proceed to step 3 of traffic scheduling policy. The current traffic scheduling policy defaults to failover based on thepriority order according to the results of active probes. When real business requests fail to retrieve content from theorigin during the backsource process, support for request retry is available. There are two request retry policies
available. For details, see Introduction to Request Retry Policy.
Policy 1: When a real business request fails to access a certain origin, it directly retries with another origin within thenext lower priority origin group. This is suitable for scenarios where the performance of both origin group 1 and origingroup 2 is similar.
Policy 2: When a real business request fails to access a certain origin, it directly retries with another origin within thesame priority origin group. This is suitable for scenarios where the performance of origin group 1 is significantly better
than that of origin group 2.

©2013-2022 Tencent Cloud. All rights reserved.

Page 8 of 52

Tencent Cloud EdgeOne

7. Taking this sample scenario as an example, policy 2 can be chosen. Click Complete to finish creating the instance.

©2013-2022 Tencent Cloud. All rights reserved.

Page 9 of 52

Tencent Cloud EdgeOne

Health Check Policies：

Last updated 2024-05-29 10:33:37
This document introduces the probe methods and their principles within health checks, the origin health determination
criteria and the calculation methods.
Note:
EdgeOne Load Balancing feature is in beta testing. If you want to use it, you can Contact Us.

Principle of Health Checks
After configuring health check policies, EdgeOne's probe nodes in different regions will send probe requests to yourorigin and determine the health status of the origin based on the response results. Health check policies consist ofprobe methods and origin health determination criteria. The probe method determines the type of probe request, while
the origin health determination criteria determine how the response results are processed.

Probe Method
Currently, supports for ICMP Ping, HTTP/HTTPS, TCP, and UDP as the four methods of probe. For more details, see
The Principle Introduction of Probe Methods. The following are the explanations for the corresponding configuration
items:
Probe Method

Applicable Scenario

Configuration
Item

Description

ICMP Ping

Only probes network
connectivity, and hostreachability.

Probe
Frequency

Required, with optional intervals of every 30
seconds, every 60 seconds, every 3 minutes,
every 5 minutes, or every 10 minutes.

©2013-2022 Tencent Cloud. All rights reserved.

Page 10 of 52

Tencent Cloud EdgeOne

HTTP/HTTPSApplicable for

Probe

Required, with optional intervals of every 30

applications that requirecontent recognition in

Frequency

seconds, every 60 seconds, every 3 minutes,
every 5 minutes, or every 10 minutes.

requests, such as web
applications and app
services.

URL

Probe Port

Required, the full URL for health checks, forexample: www.example.com/test .
Required, defaulting to port 80. It is
recommended not to modify this unless a
specific port needs to be designated.
Required, the HTTP method for health checks
is by default HEAD, with options including
GET or HEAD.
If the HEAD method is used, the server

HTTP
Methodreturns only HTTP header information, which
can reduce backend overhead and enhance
request efficiency. The corresponding origin
service must support HEAD.
If the GET method is used, the origin service
simply needs to support GET.

HTTP Status
Code

Required, the origin is considered healthy
when the status code matches the selected
status codes. By default, this includes 2XX,
with options to select: 1XX, 2XX, 3XX, 4XX,
5XX.
Disabled by default. When enabled, the probe
node will initiate another probe based on the

FollowRedirects

301/302 redirect address responded by theorigin. It Uses the status code of the final
redirection response as the determination
result for the health status. Up to 3 redirects
are supported.

CustomRequestHeaders

Optional, custom request headers can be
configured to be sent with the health checkrequests to the origin, with a maximum of 8
configurations allowed, for example: host:www.example.com .

TCP

Suitable for scenarios
where high reliability anddata accuracy are
essential, but

Probe
Frequency
Probe Port

©2013-2022 Tencent Cloud. All rights reserved.

Required, with optional intervals of every 30
seconds, every 60 seconds, every 3 minutes,
every 5 minutes, or every 10 minutes.
Required, defaulting to port 80. It is

Page 11 of 52

Tencent Cloud EdgeOne

transmission speed is ofrecommended not to modify this unless a

lesser importance, suchas file transfers andspecific port needs to be designated.

remote log-ins.
Probe
Frequency
Suitable for scenarios
where high transmission

UDP

Required, with optional intervals of every 30
seconds, every 60 seconds, every 3 minutes,
every 5 minutes, or every 10 minutes.
Required, defaulting to port 80. It is
recommended not to modify this unless a

efficiency is crucial and a
relatively lower level ofaccuracy is acceptable,

Probe Port

such as instantmessaging and online
video streaming.

Probe
RequestRequired, customize the content of the healthcheck request, with a limit of 500 characters.

Probe
Response

Required, customize the content of the healthspecific port needs to be designated.

Resultcheck request, with a limit of 500 characters.

Origin Health Determination Criteria
Choose any of the probe policies: ICMP Ping, HTTP/HTTPS, TCP, and UDP. Click Show Advanced Configuration
to configure origin health determination criteria. The following are the descriptions for each configuration item:©2013-2022 Tencent Cloud. All rights reserved.

Page 12 of 52

Tencent Cloud EdgeOne

Configuration
Item

Timeout

Description
The allowed timeout duration for a single health check request to the origin. If no response isreceived within this period, the origin is considered Unhealthy. The default is 5 seconds, with aconfigurable range of [1, 30] seconds.

Unhealthy
Threshold

HealthyThreshold

The number of consecutive probe failures required to determine an origin Unhealthy. Once thisthreshold is reached, the origin is considered Unhealthy. The default is 2 times, with aconfigurable range of [1, 5]. For example, if this value is set to 2, and an origin is initially
Healthy, upon receiving two consecutive Unhealthy probe results, the origin will be considered
Unhealthy.
The number of consecutive successful probes required to restore an origin to a Healthy state,making it available again. The default is 3 times, with a configurable range of [1, 5]. For
example, if this value is set to 3, and an origin is Unhealthy, after three consecutive Healthyprobe results, the origin will be restored to a Healthy status.

Active Probing Cycle for Origin Health Status Change©2013-2022 Tencent Cloud. All rights reserved.

Page 13 of 52

Tencent Cloud EdgeOne

For example, suppose the health determination conditions for the origin are set as follows: timeout of 5 seconds,
unhealthy threshold of 3 times, healthy threshold of 3 times, and a probe interval of every 30 seconds.
The time required to consider an origin Unhealthy would then be: 5+30+5+30+5=75 seconds.
The time required to restore the origin to a Healthy state (assuming a successful active probe response takes 1
second) would be: 1+30+1+30+1=63 seconds.

More Information
Introduction to Principle of Probe Method
ICMP Ping
HTTP/HTTPS
TCP
UDP©2013-2022 Tencent Cloud. All rights reserved.

Page 14 of 52

Tencent Cloud EdgeOne

The ICMP Ping health check mechanism is as follows:
1. EdgeOne probe node sends a Ping command to your origin.
2. If the Ping is successful, and within the backsource timeout period, the origin receives an ICMP reply, the service isconsidered normal, and the result of this check is considered healthy.
3. If the Ping fails, and within the backsource timeout period, the probe node does not receive an ICMP reply from theorigin, the service is considered abnormal, and the result of this check is considered unhealthy.
Note:
ICMP Ping requires your origin to support Ping.

©2013-2022 Tencent Cloud. All rights reserved.

Page 15 of 52

Tencent Cloud EdgeOne

The HTTP/HTTPS health check mechanism is as follows:
1. EdgeOne probe node sends an HTTP request to your origin. It requires configuration of the corresponding URL andport, with the option to include a custom HOST header.
2. If, within the backsource timeout period, the EO probe node receives an HTTP status code from the origin thatsuccessfully matches the configured HTTP status codes, the result of this check is considered healthy.
3. If, within the backsource timeout period, the EO probe node does not receive a response from the origin or receives
a status code that does not match the configured codes, the result of this check is considered unhealthy.

©2013-2022 Tencent Cloud. All rights reserved.

Page 16 of 52

Tencent Cloud EdgeOne

The TCP health check mechanism is as follows:
1. EdgeOne probe node sends a SYN connection request packet to a specific port (configurable) on your origin.
2. Upon receiving the SYN request packet, if the corresponding port on the origin is in a normal listening state, it will
respond with a SYN+ACK packet.
3. If, within the backsource timeout period, the probe node receives a SYN+ACK response packet from the origin, it
indicates that the service is running normally. The result of this check is considered healthy. The probe node thenreplies with an ACK packet to the origin and sends an RST reset packet to terminate the TCP connection.
4. If, within the backsource timeout period, the probe node does not receive a SYN+ACK response packet from theorigin, it indicates that the service is running abnormally. The result of this check is considered unhealthy. The probe
node sends an RST reset packet to the origin to terminate the TCP connection.

©2013-2022 Tencent Cloud. All rights reserved.

Page 17 of 52

Tencent Cloud EdgeOne

The UDP health check mechanism is as follows:
1. EdgeOne probe node sends a customized probe packet to a specific port (configurable) on your origin.
2. If, within the backsource timeout period, the probe node receives a customized response packet from the origin, it
indicates that the service is running normally. The result of this check is considered healthy.
3. If, within the backsource timeout period, the probe node does not receive a customized response packet from theorigin or receives a response packet that does not conform to the defined content, it indicates that the service isrunning abnormally. The result of this check is considered unhealthy.
Note:
Both the request content and response content are customized, and you need to configure the corresponding requestresponse content on your origin.

Probe Request Identification
Active probes do not carry special request identifiers. When you choose ICMP Ping or TCP probes, there are no
related features. When you choose UDP probes, customized content can be configured to serve as identifiers. For
HTTP/HTTPS probes, separate customized request headers can be configured to serve as identifiers.

©2013-2022 Tencent Cloud. All rights reserved.

Page 18 of 52

Tencent Cloud EdgeOne

Viewing the Health Status of Origin Server：

Last updated 2024-05-29 10:33:37
The node probe results will display the outcomes of probes initiated by EdgeOne from various nodes and regions
within the global availability zones towards the current origin group. Users can view these probe results to find whether
the origin is healthy across different zones.
Note:
EdgeOne Load Balancing feature is in beta testing. If you want to use it, you can Contact Us.
1. Log in to the EdgeOne console. In the left menu bar, click the Site List. Within this list, click the Site need to be
configured to go to the details page.
2. On the site details page, click Origin Settings > Load Balancing.
3. On the Load Balancing page, click the desired Load balancer.

4. In the instance details page, click View details.

5. In the node probe results, nodes are differentiated by the following three colors:
Green Node: Indicates that the probe node in the region has considered all origins in the origin group to be healthy.
Red Node: Indicates that the probe node in the region has considered one or more origins in the origin group to beunhealthy.

©2013-2022 Tencent Cloud. All rights reserved.

Page 19 of 52

Tencent Cloud EdgeOne

Gray Node: Indicates that the probe node in the region cannot probe any origins. Probing is done at the IP level,
meaning if the origin is a domain, the domain will be resolved into an IP before it probes. This situation usually occurs
if you have entered an incorrect domain origin which cannot be resolved into an IP. In this case, it is recommended tocheck for potential spelling mistakes in the origin domain or whether the corresponding domain has expired.

Note:
Probe nodes in different regions make independent decisions. Edge nodes will route requests back to the origin basedon the probe results from the nearest probe nodes in each region.
For example: If your origin is in Hong Kong (China), and the probe node in Singapore considers the origin to beunhealthy whereas the probe node in Germany considers it to be healthy, traffic from the Singapore region will not berouted to that origin, while traffic from the Germany region will continue to be directed to that origin.
In the scenario described above, you can refer to the probe results from other regions for a comprehensive view. If
only a few nodes consider the origin to be unhealthy, it might be due to network fluctuations in certain areas. If the
majority of nodes consider the origin to be unhealthy, it is recommended to check whether the origin has
malfunctioned.

©2013-2022 Tencent Cloud. All rights reserved.

Page 20 of 52

Tencent Cloud EdgeOne©2013-2022 Tencent Cloud. All rights reserved.

Page 21 of 52

Tencent Cloud EdgeOne

Related References
Load Balancing-Related Concepts：

Last updated 2024-05-29 10:33:37
This document introduces the relevant concepts involved in Load Balancing.
Note:
Tencent Cloud EdgeOne Load Balancing feature is in beta testing. If you want to use it, you can Contact Us.

Load Balancer
A load balancer is a virtual concept, comprising Origin groups and health check policies. Within a single loadbalancer, up to ten origin groups can be configured in priority order, accompanied by one health check policy. The
load balancer intelligently directs business traffic based on probe results and the configured traffic scheduling policy.

©2013-2022 Tencent Cloud. All rights reserved.

Page 22 of 52

Tencent Cloud EdgeOne

Origin GroupAn origin group is the smallest unit of origin configuration within the Load Balancing. You can add one or more origins.
When you add multiple Origin Servers, you can configure weights to adjust traffic load. For more details, see Origin
Group Configuration.

Health Check Policy
The health check policy consists of probe methods and health assessment criteria. Currently, four probe methods aresupported: ICMP Ping, HTTP/HTTPS, TCP, and UDP. For more details, see Detailed Health Checks.

Traffic Scheduling Policy
The traffic scheduling policy only takes effect when the health check policy is enabled. Currently, it supports a Failoverby-Priority-Order policy, that is, based on probe results, it disables failed origins and routes traffic to healthy ones
according to the priority order of origin groups.

Request Retry Policy
In the event of a request failure to a particular origin during normal business operations, the Load Balancing feature,guided by its request retry policy, can schedule the request to another origin for a retry. This helps reduce business
request failures due to network issues or origin malfunctions. For more details, see the Introduction to Request Retry
Policy.

©2013-2022 Tencent Cloud. All rights reserved.

Page 23 of 52

Tencent Cloud EdgeOne

Introduction to Request Retry Strategy：

Last updated 2024-05-29 10:33:37
Load Balancing is capable of redirecting a request to an alternative origin for retrial when a request to an initiallydesignated server fails, in accordance with the retry policy. This reduces business request failures caused by network
issues or origin fails.
Note:
EdgeOne Load Balancing feature is in beta testing. If you want to use it, you can Contact Us.
Actual business requests may fail due to the following reasons:
1. Origin Failure and Have Not Actively Probe to Disable: After health check policies are configured, active
probe is conducted periodically. Traffic is directed based on the results of the previous probe until new results areavailable. If an origin becomes unhealthy between two probes, business traffic might still be directed to the unhealthy
origin. This leads to business request failure.

2. Network Jitter: The origin is healthy, but network issues occur during the access. This leads to business request
failure.
Note:Request failures include origin connection establishment failures and origin response reception failures.

For the situations mentioned above, EdgeOne provides the following two fallback request retry policies:
Policy 1: When a real business request fails to access a certain origin, it directly retries with another origin within thenext lower priority origin group. This is suitable for scenarios where the performance of both higher and lower priority
origin groups is similar.
Policy 2: When a real business request fails to access a certain origin, it directly retries with another origin within thesame priority origin group. This is suitable for scenarios where the performance of the higher priority origin group is©2013-2022 Tencent Cloud. All rights reserved.

Page 24 of 52

Tencent Cloud EdgeOne

significantly better than that of the lower priority origin group.

©2013-2022 Tencent Cloud. All rights reserved.

Page 25 of 52

Tencent Cloud EdgeOne

Origin Group Configuration：

Last updated 2024-08-01 21:32:16

Overview
Manage business origins in the form of origin groups. The origin groups configured here can be used in functions suchas adding acceleration domain names and L4 proxy.

Create Origin Group
1. Log in to the EdgeOne console and click Site List in the left sidebar. In the site list, click the target site to enter thesite details page.
2. On the site details page, click origin configuration > origin group.
3. Click Create origin group.
4. Fill in 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, andcan be used for site acceleration services (such as Domain Name Service and rule engine) and L4 proxy.
Note:
After the configuration is complete, the origin group type cannot be modified.

©2013-2022 Tencent Cloud. All rights reserved.

Page 26 of 52

Tencent Cloud EdgeOne

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 the weight of an origin is set to 0, no origin-pull requests will beallocated to that origin. Other non-zero weight origins will be allocated origin-pull requests based on their respective
weight ratios.
2. If you do not set a weight, all origins in the origin group should not set weights at the same time. In this case, if"smart acceleration" is not enabled, EdgeOne will distribute origin-pull requests equally to each origin. If "smart
acceleration" is enabled, EdgeOne will select the best quality origin for each origin-pull request.

6. Click Create to complete the origin group creation.

©2013-2022 Tencent Cloud. All rights reserved.

Page 27 of 52

Tencent Cloud EdgeOne

Origin-pull configuration
Configuring Origin-Pull HTTPS：Last updated 2023-12-13 11:10:42

Overview
You can specify the protocol that EdgeOne uses in the origin-pull request.
In scenarios that requires a high level of security, HTTPS can be used to access a website to ensure the security ofwebsite data. When HTTPS is specified as the origin-pull protocol, all origin-pull requests from EdgeOne to the origin
use HTTPS, which prevents data tampering or theft during transmission.
In scenarios where fast response is required, HTTP can be used for origin-pull requests to speed up website access.
When HTTP is specified as the origin-pull protocol, you can avoid complex SSL handshakes and other operations
between EdgeOne and the origin, thus improving the website access speed. If your origin does not support HTTPS,
please select HTTP.

1. An EdgeOne node initiates an origin-pull request by using the specified origin-pull protocol.
2. The origin responds to the request and establishes a connection by using the same protocol as the request.
Note:
The configuration priority of the rule engine is superior. If the origin protocol rule is configured simultaneously within thedomain name service and the rule engine, the final standard is determined by the rule engine.

Scenario 1: Configuring origin-pull HTTPS for multiple domainnames in batches in the rule engine
If you need to uniformly change the origin-pull protocol to origin-pull HTTPS for multiple domain names, such as
www.example.com , vod.example.com and image.example.com , please refer to the following steps:
1. Log in to the EdgeOne console and click Site List in the left sidebar. In the site list, click the target site.
2. On the site details page, click Rule Engine.

©2013-2022 Tencent Cloud. All rights reserved.

Page 28 of 52

Tencent Cloud EdgeOne

3. On the rule engine management page, click Create rule.
4. On the rule editing page, enter the rule name and select Host matching type to match the request of the specified
domain name. In the current scenario, select domain names www.example.com , vod.example.com andimage.example.com .
5. Click on Action > Select Box, select Origin-pull HTTPS from the dropdown action list that appears.

6. Click on Save and Publish to finalize this rule configuration.

Scenario 2: Configuring origin-pull HTTPS for the specified domain
nameIf you need to specify a domain name to modify the origin-pull protocol into origin-pull HTTPS, such as
www.example.com, please follow these steps:
1. Log in to the EdgeOne console, click Site List on the left sidebar, and click the Site to be configured in the site list,
2. Choose Domain Name Service > Domain Name Management on the Site Details page.
3. Select the domain name that needs to be modified and click Edit on the Domain Management page.

4. In the origin-pull protocol, select HTTPS and click Complete to finish the modification.

©2013-2022 Tencent Cloud. All rights reserved.

Page 29 of 52

Tencent Cloud EdgeOne©2013-2022 Tencent Cloud. All rights reserved.

Page 30 of 52

Tencent Cloud EdgeOne

Host Header Rewrite：

Last updated 2023-10-11 10:28:05

Overview
Host header rewriting enables you to rewrite the host header to the actual origin domain when the origin domain isdifferent from the acceleration domain in the load balancing task.

Directions
1. Log in to the EdgeOne console. Select Origin Configuration >Rule Engine on the left sidebar.
2. On the rule engine page, select the target site and click

to configure host header rules as needed.
3. On the rule engine page, select Host for the match type and Rewrite host header for the action, and configure
other parameters as needed. Click Save and publish or Save only.
Note
Supported match types: "Host".

©2013-2022 Tencent Cloud. All rights reserved.

Page 31 of 52

Tencent Cloud EdgeOne

Controlling Origin-pull Requests：

Last updated 2023-08-30 15:09:23

Overview
By default, when origin-pulling, all query strings and Cookies within the request will be retained. If your business origin
only allows specified query strings or Cookie information to be carried in the origin-pull request, you can ensure thenormal origin-pull request by deleting the specified origin-pull request parameters.

Directions
For example, Client requests Request URL: http://www.example.com/path/demo.jpg?
key1=a&key2=b&key3=c&key4=d , and only key1=a parameter needs to be retained when origin-pulling. You
can follow the steps below to configure:
1. Log in to the EdgeOne console, click on the site list in the left menu bar, and click on the site to be configured within
the site list.
2. On the site details page, click on the rule engine.
3. On the rule engine Management page, click Create rule to enter the edit page of the new rule.
3.1. On the rule edit page, select the matching type as HOST equals www.example.com .
3.2. Click on the action, and in the pop-up operation list, select the operation as origin-pull request parametersettings.
3.3. Select the mode as retaining specified parameters, Enter the parameters key1 and key2 to be retained, up
to 10 parameters are allowed.

©2013-2022 Tencent Cloud. All rights reserved.

Page 32 of 52

Tencent Cloud EdgeOne

4. Click Save and Publish to complete the rule Configuration.

©2013-2022 Tencent Cloud. All rights reserved.

Page 33 of 52

Tencent Cloud EdgeOne

Redirect Following During Origin-Pull：

Last updated 2023-08-30 15:08:04

Overview
Under normal circumstances, when the origin returns a 301/302 request, the node will return the status code to theclient by default, and the client will redirect to the corresponding resources for access. EdgeOne supports follow origin
redirects. When enabled, if the node receives a 301/302 status code during origin-pull, it will actively follow theredirect (not exceeding the set maximum redirects) to the specified address until the corresponding file is obtained,
and then respond to the client with the actual resources, which can improve the user's access response speed.
For example: The client accesses the URL https://a.example.com/test.jpg , the origin A redirects the
URL 302 to https://b.example.com/test.jpg , and the domain a.example.com has accessed theEdgeOne Service, while b.example.com has not yet accessed the acceleration service. Then:
Without enabling origin-pull follow redirect: After the client initiates the visit, if there is no cache in the EdgeOne
node, it will visit the origin A and receive the 302 status code, and then respond to the client with the status code, andthe client will directly request the origin B for the corresponding resources. At this time, since the origin B has notaccessed the acceleration service, the client's self-initiated access speed is slower, and the obtained file cannot becached. When other users access the same file, the process needs to be repeated.
Enable origin-pull follow redirect: After the client initiates the visit, if there is no cache in the EdgeOne node, it willvisit the origin A and receive the 302 status code, and then, according to the status code and the corresponding
address, directly request the origin B for the corresponding resources, and cache the resources in the node. This
process is carried out by the EdgeOne node for origin-pull requests, the request speed is faster, and the obtained filecan be cached in the node. When other users access the same file, there is no need to repeat the origin-pull, and thefile can be directly hit and responded to the client.

©2013-2022 Tencent Cloud. All rights reserved.

Page 34 of 52

Tencent Cloud EdgeOne

Directions
For example: If you need to enable origin-pull follow redirect for the specified domain www.example.com , with amaximum of 3 redirects. You can refer to the following steps:
1. Log in to the EdgeOne console, click on the site list in the left menu bar, and click on the site to be configured in thesite list.
2. On the site details page, click on the rule engine.
3. On the rule engine management page, click Create Rule to enter the editing page of the new rule. In this scenario,
you can follow the steps below:
3.1. On the rule editing page, select the matching type as HOST equals www.example.com .
3.2. Click on the action, and in the pop-up operation list, select the operation as follow origin redirect.
3.3. Click on the switch, click on the switch to enable, and set the maximum redirects to 3 times. The related
configuration instructions are as follows:
Maximum redirects: You can set it between 1-5 times. Within the maximum redirects, the node will follow the redirect
address until the corresponding resources are obtained. If the maximum redirects are exceeded, the corresponding
status code will be directly responded to the client.

©2013-2022 Tencent Cloud. All rights reserved.

Page 35 of 52

Tencent Cloud EdgeOne

4. Click on Save and Publish to complete the rule configuration.

©2013-2022 Tencent Cloud. All rights reserved.

Page 36 of 52

Tencent Cloud EdgeOne

HTTP/2 Origin-Pull：

Last updated 2023-08-30 15:05:42

Overview
Support EdgeOne nodes to origin-pull using HTTP/2 protocol. HTTP/2 (i.e., HTTP 2.0, Hypertext Transfer Protocol
version 2) is the second major version of the HTTP protocol, which can effectively reduce network latency andimprove site page loading speed.

：

Note

1. When enabled, the origin must support HTTP/2 protocol access.
2. If you need to configure HTTP/2 access, please refer to HTTP/2.

Directions
If you need to enable or disable HTTP/2 origin-pull for the specified domain www.example.com , you can follow
the steps below:
1. Log in to the EdgeOne console, click on the site list in the left sidebar, and click on the site you need to configure
within the site list.
2. On the site details page, click on the rule engine.
3. On the rule engine management page, click on create rule to enter the new rule editing page.
3.1 On the rule editing page, select the matching type as HOST equals www.example.com .
3.2 Click on the action, and in the pop-up operation list, select the operation as HTTP/2 origin-pull.
3.3 Click on the switch to enable/disable HTTP/2 origin-pull.

©2013-2022 Tencent Cloud. All rights reserved.

Page 37 of 52

Tencent Cloud EdgeOne

4. Click on Save and Publish to complete the rule configuration.

©2013-2022 Tencent Cloud. All rights reserved.

Page 38 of 52

Tencent Cloud EdgeOne

Range GETs：

Last updated 2024-01-02 09:59:31

Overview
Range GETs can be enabled to reduce the consumption of large file origin-pulls and response time.
Why can Range GETs improve the efficiency of large file delivery?
When caching large files, nodes will split them into smaller parts in order to improve cache efficiency. All parts cachedexpire at the same time and follow the node cache TTL configuration. Range requests are also supported. For
example, if a client request carries the HTTP header Range: bytes = 0-999 , only the first 1000 bytes of the file
will be returned to the user.
If Range GETs is enabled: When parts of the file are requested and their caches expire, nodes only pull and cache therequested parts and return them to the user, so that origin-pull consumption and response time are greatly reduced.
If Range GETs is disabled, when the client requests only parts of a file, the node will pull only the requested parts
according to the Range header in the client request, cache them, and return them to the client at the same time.
However, this may not be able to achieve the optimal performance. In large file scenarios, we recommend you enable
Range GETs.

Use Cases
You can use Range GETs to cache large static files in either of the following cases: The origin server supports Range
requests, or you use a Tencent Cloud COS origin server and do not apply any data processing methods such asimage processing.

Notes
The origin server must support Range requests, or the origin-pull may fail.
The origin-pull may fail if Range GETs is enabled for small static files, or if you enable it while using a Tencent Cloud
COS origin server and data processing methods such as image processing.

Directions©2013-2022 Tencent Cloud. All rights reserved.

Page 39 of 52

Tencent Cloud EdgeOne

For instance, you have a video service website that provides online video watching throughvideo.example.com . The videos are mainly long videos with large files. In order to reduce traffic consumption oflarge files and improve origin-pull speed, you need to support range requests and origin-pull. You can perform thefollowing steps:
1. Log in to the EdgeOne console, click Site List in the left sidebar and click the Site to be configured in the site list.
2. On the site detail page, click on Rule Engine.
3. On the rule engine management page, click on Create rule to enter the new rule's editing page. In this scenario,
you can operate as follows:
3.1 On the rule editing page, select the Matching type as HOST equals video.example.com .
3.2 Click on Action, in the displayed operation list, choose the operation as Range GETs.
3.3 Click on On/Off to enable Range GETs.

4. Click on Save and publish to complete the configuration of this rule.

©2013-2022 Tencent Cloud. All rights reserved.

Page 40 of 52

Tencent Cloud EdgeOne

Related References
ld Version Origin Group Compatible Related
Issues：Last updated 2023-10-24 15:45:49
The origin group has carried out a product capability upgrade since October 24, 2023. After the upgrade, the oldversion of the origin group will be processed for compatibility in the following ways. At the same time, we also suggest
you switch to the usage of the new version of the origin group.

Origin type & Configuration method compatibility
The new version of the origin group will no longer distinguish between self-owned origin, object storage origin,and Tencent Cloud COS type origin. The original origin groups with origin type of object storage and Tencent
Cloud COS will be automatically updated to the new version of dedicated HTTP origin group, and the original origingroups with self-owned origin type will be automatically updated to the universal origin group.
The origin group will no longer support the configuration of origin-pull by region/protocol. If you have previously
configured related origin-pull rules by region/protocol, the rules will be migrated to the rule engine as shown below:©2013-2022 Tencent Cloud. All rights reserved.

Page 41 of 52

Tencent Cloud EdgeOne©2013-2022 Tencent Cloud. All rights reserved.

Page 42 of 52

Tencent Cloud EdgeOne

Origin group port migration description
The new version of the origin group will no longer support port configuration. All port configurations will be migrated tothe service configuration entry, such as L4 proxy or Domain Management.

©2013-2022 Tencent Cloud. All rights reserved.

Page 43 of 52

Tencent Cloud EdgeOne

Primary and Standby Origin Configuration Instructions
In the Domain Management and Rule Engine - Modify Origin, directly configuring primary and standby origins is
no longer supported. Existing configurations will not be affected, but modifications are no longer supported. If you
currently have a demand for primary and standby origin configurations, please contact us for support.

©2013-2022 Tencent Cloud. All rights reserved.

Page 44 of 52

Tencent Cloud EdgeOne

VOD Origin Server Details：

Last updated 2024-07-29 15:38:48

Origin Server Introduction
Tencent Cloud Video on Demand (VOD) offers integrated high-quality media services, such as production and upload,
storage, transcoding, Media Processing Service (MPS), media AI, copyright protection, and play for media, such as
audio, video, and images.

VOD Origin Server Advantages
Advantage
Multi-dimensional
cost optimization

Description
VOD provides media services with strategies such as cold storage and smart bitrate
reduction. By optimizing costs in detail according to real-time media playback, it
effectively saves storage and distribution costs for users.

Scenario-basedtranscoding

VOD offers superior transcoding capabilities for various industry scenarios. Utilizing
technologies like intelligent scene recognition, dynamic encoding, and the CTU/row/frame
three-level bitrate precision control model, it achieves higher subjective image quality at alower bitrate (nearly 50%), realizing high image quality at a low bitrate, and saves
network traffic and storage costs.

Stable storage

VOD supports backup storage of video files across architectures and devices, andprovides cross-region disaster recovery and user resource isolation, greatly enhancing
storage stability.
VOD improves data transfer efficiency and stability in poor network conditions throughHigh-quality
uploadvarious upload acceleration measures, such as scheduling optimization, global multistorage park coverage optimization, link supplementation, transmission optimization, andthe Quick UDP Internet Connections (QUIC) protocol, improving the upload speed andsuccess rate.

Copyright
protection

Copyright protection features of VOD include the hotlink protection, ghost watermark,
HTTP Live Streaming (HLS) private encryption, and commercial-grade Digital Rights
Management (DRM) encryption, providing high-level security for content rights owners.

Audio/video
distribution
optimization

When users select the VOD origin server, the EdgeOne acceleration service automaticallyenables the pre-fetching capability of audio and video files by default. It supports segment
fetching and caching of HLS/DASH/MP4/FLV format files to edge nodes when a client
request is made, enhancing the response speed of video files, thereby©2013-2022 Tencent Cloud. All rights reserved.

Page 45 of 52

Tencent Cloud EdgeOne

optimizing the time it takes to start playing videos and reducing the rate ofplayback stuttering.

VOD Origin Server Use Cases
Application
Scenario

Online education

Ecommerce apps

Scenario Description
Online education refers to a teaching method that uses the network as a medium, wherestudents and teachers conduct educational activities online. Platforms generally have alarge number of audio and video teaching resources, most of which are recorded anduploaded by registered teachers. VOD offers features like multi-end playback, smart
subtitles, copyright protection, time shifting, VOD to live streaming, and content review forthis scenario, helping users quickly build an audio and video teaching platform.
Ecommerce apps are online transaction platforms where enterprises and individuals canmarket and sell their products. Sellers typically produce and upload product images andvideos to better showcase their products. Buyers can also upload images and videos toshare feedback about their shopping experience or write product reviews. VOD provides
features such as HD with low bitrate, smart screenshot cover, multi-bitrate smart
switching, upload acceleration, and tag classification for this scenario, thereby helping
users better showcase their ecommerce products.

TV stations andover-the-top (OTT)

TV stations and OTT primarily offers streaming media services based on TV terminals.
VOD provides features for this scenario, such as Top Speed Codec (TSC) transcoding,multi-bitrate smart switching, copyright protection, media AI recognition, VOD to live
streaming, and video production, helping users quickly build a smart media asset libraryand offering diverse applications like cloud editing and video directing.

Live streaming
appsLive streaming apps allow hosts to broadcast, deliver commentary, or perform live overthe network, such as live show streaming, game live streaming, live classes, live
shopping, and live Q&A. VOD provides capabilities such as live recording, time shifting,live editing, TSC, and VOD to live streaming, to help users quickly establish a stable andreliable live streaming platform.

Use Limits
Using the VOD origin server will automatically provide more suitable distribution acceleration configurations for yourmedia content. Therefore, when using the rule engine and site acceleration configurations for a VOD origin server, theVOD default configurations will be used for some operations to offer better distribution acceleration effects. To prevent©2013-2022 Tencent Cloud. All rights reserved.

Page 46 of 52

Tencent Cloud EdgeOne

conflicts between custom configurations and default settings, some site acceleration configuration and rule engine
operations will not be supported. The detailed limits are as follows:Note:
To modify the following unsupported configuration items for the VOD origin server, contact us.
FeatureModuleOperation
Type

Operation

Rule engine

Limit
Custom configurations are not supported. If they are

Node Cache TTL

Browser Cache
TTL

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Custom Cache Key

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Status Code Cache
TTL

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Cache Prefresh

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Offline Cache

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

HTTP/2Custom configurations are supported.

Enable HTTP/3

Custom configurations are supported.

WebSocket

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Maximum Upload
Size

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Smart Compression

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Cache
configuration

Network
optimization

configured, the configuration content will not takeeffect.

©2013-2022 Tencent Cloud. All rights reserved.

Page 47 of 52

Tencent Cloud EdgeOne

Smart Acceleration

HTTPS
optimization

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

HTTP/2 Origin-Pull

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Origin-Pull Timeout

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Forced HTTPS
AccessCustom configurations are supported.

Enabling HSTS

Custom configurations are supported.

Configuring
SSL/TLS Security

Custom configurations are supported.

Enabling OCSP
Stapling

Custom configurations are supported.

Configuring OriginPull HTTPS

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Modifying HTTP
Response Headers

Custom configurations are supported.

Client IP
Geolocation Header

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Client IP
Geographical
Location

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Modifying HTTP
Request Headers

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Host Header
RewriteCustom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Advanced

Access URL

Custom configurations are supported.

configuration

Redirection

HTTP
headermodification©2013-2022 Tencent Cloud. All rights reserved.

Page 48 of 52

Tencent Cloud EdgeOne

Token
Authentication

Supports custom A/D Authentication Method, does
not support custom B/C Authentication Method

Origin Server
Modification

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Origin URL Rewrite
Configuration

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Controlling Originpull Requests

Redirect Following
During Origin-Pull

Siteacceleration

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.
Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Custom Error Page

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Range GETs

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

HTTP Response

Custom configurations are supported.

Query string

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Ignore case

Custom configurations are not supported. If they are
configured, the configuration content will not takeeffect.

Cache
configuration©2013-2022 Tencent Cloud. All rights reserved.

Page 49 of 52

Tencent Cloud EdgeOne

Collect EdgeOne origin-pull node IP：

Last updated 2023-12-15 09:54:21
To obtain the EdgeOne's IPs for requesting origin, which can be used to set these EdgeOne's IPs as an allowlist in theorigin firewall, only allowing fixed source (IP) requests to the origin, thus implementing protection for the origin.

Use Guide
1. Directly access https://api.edgeone.ai/ips through a browser or curl command. This will collect all IPv4 and IPv6
origin-pull node IP addresses of EdgeOne in the Global availability zone. The responded result is UTF-8 encoded
plain text, with one IP segment per line.
2. If you only need to obtain the origin-pull node IP of a specified region or a specified IP Type, you can also filter theorigin-pull node IP by carrying a specified query string. The supported query strings are as follows:
Query string

Explanation

versionSpecifies the Type of origin-pull node IP address to be collected, with the following values:v4: All IPv4 origin-pull node IP addresses
v6: All IPv6 origin-pull node IP addresses
By default, all IPv4 and IPv6 IP addresses are returned when this parameter is notincluded.

area

Specifies the region of the origin-pull node IP to be collected, with the following values:
global: All origin-pull node IP addresses in the Global availability zone
mainland-china: All origin-pull node IP addresses in the Chinese mainland availability
zone
overseas: All origin-pull node IP addresses in the Global availability zone (excluding
Chinese mainland)
By default, all origin-pull node IP addresses in the Global availability zone are returned
when this parameter is not included.

：

Note

1. In general, it is suggested to select and obtain the origin-pull node IP address of the corresponding region based onyour site's service area. For example, if the site's service area is in the Chinese mainland availability zone, you canobtain the origin-pull node IP address within the Chinese mainland availability zone, and the same applies to otherservice areas.
2. This function is mutually exclusive with the origin protection function. If you need to collect the latest origin-pull IP
through the method in this Document, please confirm that you have turned the business origin protection function Off.

©2013-2022 Tencent Cloud. All rights reserved.

Page 50 of 52

Tencent Cloud EdgeOne

Request example
If you want to obtain all IPv6 origin-pull node IPs in the Global availability zone (excluding Chinese mainland), you canquery the origin-pull IP address under this condition by carrying version=v6&area=overseas in the request
URL. The specific URL is: https://api.edgeone.ai/ips?version=v6&area=overseas

The response result example is as follows (this result is for reference only, please refer to the real-time request result
for the actual origin-pull IP):©2013-2022 Tencent Cloud. All rights reserved.

Page 51 of 52

Tencent Cloud EdgeOne

240d:c010::/28
2001:ee0:324b:100::/64
2405:3200:101:63::/64
2405:4800:a601::/64
2602:ffe4:c02:1001::/64
2602:ffe4:c12:101::/64
2602:ffe4:c12:105::/64
2602:ffe4:c15:124::/64
2602:ffe4:c18:c003::/64
2602:ffe4:c18:c201::/64
2602:ffe4:c18:c203::/64
2602:ffe4:c27:1003::/64
2604:980:4002:2::/64
2604:980:5003:2::/64
2604:980:7002:6::/64
2a02:b60:2001::/64©2013-2022 Tencent Cloud. All rights reserved.

Page 52 of 52