Tutorials

This document describes how to connect your domain name to EdgeOne and enable domain acceleration.

This document describes how to change the CNAME of a domain name.

Using alias domain names makes it easy for SaaS businesses to sync the configuration of one domain name to others to achieve batch connection.

This document describes how to achieve business disaster recovery by using EdgeOne alias domain names. If a domain name becomes unavailable due to, for example, DNS exceptions, the alias domain name can provide the service instead.

EdgeOne enables Gzip or Brotli compression globally by default. When the client request header carries Accept-Encoding: br, gzip or Accept-Encoding: br or Accept-Encoding: gzip, the node will intelligently compress files based on their Content-Type.

Smart acceleration can adjust and optimize network paths in real-time. After enabling this function, EdgeOne will detect node network latency in real-time, select the best access path through intelligent algorithms, and dynamically adjust resource allocation and utilization according to the real-time network conditions, to help improve user experience and ensure business continuity.

EdgeOne supports clients to initiate requests using the HTTP/2 protocol. HTTP/2 (i.e., HTTP 2.0, the second version of the Hypertext Transfer Protocol) is the second major version of the HTTP protocol, which can effectively reduce network latency and improve site page loading speed.

HTTP/3 (HTTP over QUIC) is the next-generation Internet transmission protocol, designed to solve the head-of-line blocking issues in HTTP/2. Instead of being based on TCP, HTTP/3 uses the QUIC protocol, which is based on the UDP protocol.

EdgeOne supports one-click enable of IPv6 access, allowing IPv6 clients to access nodes using the IPv6 protocol.

EdgeOne supports WebSocket protocol access, which enables the server to actively push data to the client. WebSocket protocol is a persistent protocol based on TCP, which implements full-duplex communication between the client and the server, allowing the server to actively send information to the client.

Real client IP header allows you to create a custom origin-pull HTTP request header that carries the real client IP information.

EdgeOne provides support to redirect to a specified custom page and return a 302 status code when the origin server responds with specific error statuses. This helps your site inform users of the current website status by the customized error page, avoiding uncertainty regarding the specific cause and resolution when a request error occurs.

Support customization/adding/deleting HTTP node response headers (responding to the customer's direction), modifying HTTP node response headers will not affect the node cache.

When Edgeone nodes origin-pull, if the origin needs to obtain some specific information through the HTTP request header for business logic judgment or data analysis, such as: client device type, acceleration service provider. This can be achieved by customizing/adding/deleting HTTP origin-pull request headers (node origin-pull direction), where the header value supports variables, please refer to EdgeOne preset variables for details.

You can specify the protocol that EdgeOne uses in the origin-pull request.

To obtain the EdgeOne's IPs for requesting origin, which can be used to set these EdgeOne's IPs as an allowlist in the origin firewall, only allowing fixed source (IP) requests to the origin, thus implementing protection for the origin.

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

This document describes how to create a simple edge function and use the function to redirect a request to another URL and return the custom response header.

This document describes how to create, edit, and delete an edge function, and how to configure the rules that trigger the function.

This document guides you how to manage function triggering rules.

This document describes how to the convert image format by using edge functions without changing the original client request URL.

EdgeOne Service analyzes L7 (application layer) access log data to provide you with multi-dimensional, visualized traffic analysis, including time trend curves of traffic, requests, and other indicators, as well as country/region distribution and TOP rankings.

EdgeOne provides multi-dimensional, visualized cache analysis by analyzing L7 (application layer) access log data, including time trend curves of traffic, requests, and other metrics, cache status distribution, and TOP rankings.

The Site Security Overview focuses on displaying the main security risks faced by the site.

Web security analysis provides fine-grained analysis tools for security events, offering reference for you to formulate or adjust security policies.

EdgeOne provides data analysis and display of user access to L4 (transport layer) proxy instances by analyzing L4 access logs, including traffic, connection count, connection duration, and other data, helping you better monitor the operation of L4 proxy instances.

This page mainly displays the number of resolution requests received by EdgeOne DNS. Only data from sites that support NS mode access is available.

This article introduces how to reasonably use various configurations on EdgeOne, combined with your actual business scenarios for tuning, and improve the cache hit rate of files within the site.

When you need to point the Request URL of the same path to different files based on request parameters, cookies, or HTTP request headers, or point the Request URL with different parameters to the same file, the custom Cache Key supports customizing the Cache Key identification of resources in the node, including concatenating query strings, concatenating HTTP headers or Cookie information, etc., so that the Request URL can correctly obtain the corresponding cached resources according to different scenarios.

After the cache resources expire within the EdgeOne node, EdgeOne will follow the origin to obtain the latest resource files when receiving the corresponding client requests, which may cause a large increase in origin-pull requests during peak periods. The cache pre-refresh function can verify the validity of cache resources before they expire, without waiting for expiration, which helps maintain the real-time nature of resources and respond to requests more quickly. The cache pre-refresh time can be configured according to the percentage of the file cache TTL.

The Client browser cache TTL is the cache duration of resources in the browser, which by default follows the origin's Cache-Control headers. You can control the cache duration of resources in the browser by configuring EdgeOne's browser cache TTL without modifying the origin configuration.

When your resource content is cached to the EdgeOne edge node, during the cache validity period, users accessing the resource will be directly responded by the EdgeOne edge node without triggering a return to the origin.

The cache pre-warming function allows resources to be cached on EdgeOne in advance. In this way, even if the client requests for the first time, it can be directly responded from the cache of EdgeOne without the need to follow the origin.

Cache Key is used to determine whether the file resources accessed by users hit the edge caching content of EdgeOne, and it is the unique identifier of cached resources within the node.

This document describes how to configure the DNS record on EdgeOne.

This document describes how to modify the DNS server addresses when you select the NS access mode. EdgeOne provides integrated analysis, acceleration, and security services for your site only when you have completed the modification.

This document will introduce the advanced configuration principles and methods such as DNSSEC, custom NS, CNAME acceleration supported by EdgeOne.

This document describes how to create and configure an L4 proxy instance.

Tencent Cloud EdgeOne allows you to configure multiple forwarding rules for an L4 proxy instance. This document describes how to import and export multiple forwarding rules at a time.

You can use this document to learn how to get the TCP client IP via TOA when using L4 proxy.

If the TCP protocol is used on the origin, it is recommended to add a Nginx server that supports Proxy Protocol V1/V2 in front of the application server to obtain real client IPs.

You can use this document to learn how to Parsing Real Client IPs on Application Server in L4 proxy.

This document describes supported matching types in Rule Engine

The rule engine is designed to meet more flexible and fine-grained business requirements through a rich rule language. You can customize the match type as needed and apply it to the corresponding operations.

The variables of the rule engine allow you to dynamically extract and process data within request. These variables can not only store static values but also use for specific fields or information in the request, the value of which may change when processing each request.

You can use this document to learn How to use Exclusive DDoS Protection.

If you find that all your attacks come from a specific region, or your business only allows access from specific regions and does not trust access from other regions, EdgeOne supports one-click blocking in the cleaning room by specifying a list of regions based on the source IP geographic region, helping you to custom block access requests from specified regions. After enabling region blocking, traffic from the blocked region to the EdgeOne site will be discarded. Supports multi-region and country traffic blocking.

EdgeOne DDoS protection service supports controlling client source IP blocking or releasing access requests by configuring IP blocklist and allowlist, thus limiting users accessing your application resources.

The DDoS attack traffic alert function allows users to set custom attack traffic rate alert thresholds for DDoS protection instances. When the detected attack traffic rate exceeds the set threshold, the system will send an alert notification to help users understand and respond to potential DDoS attacks in a timely manner.

EdgeOne supports one-click blocking of source traffic to the site by protocol type. You can configure ICMP protocol blocking, TCP protocol blocking, UDP protocol blocking, and other protocol blocking. After the configuration is complete, when the attack traffic is detected with related Access request, it will be directly truncated.

EdgeOne supports protection against connection-based attacks, automatically blocking clients with abnormal connection behavior.

To avoid CC attacks, EdgeOne provides a pre-set CC attack protection strategy and enables it by default to ensure the stability of your site online.

Custom rules support matching client requests based on single rule matching conditions or multiple matching conditions. By allowing, intercepting, redirecting, and returning custom pages, you can control the request strategy of matched requests, which can help your site more flexibly limit the content that users can access.

In site operation, problems such as malicious resource occupation, business abuse, and brute force cracking often occur. If these problems are ignored, they will lead to a decline in service quality, generate high-cost bills, and may even cause sensitive data leakage.

Exception rules provide a centralized allowlist configuration option, allowing for quick configuration of valid requests to be released, avoiding interception by other modules.

Many public or commercialized programs, including search engine crawlers, have fixed or default User-Agent header features and have specific purposes. Bot management policies include most public bot type features, and you can directly manage bot tools that meet these features.

In addition to analyzing the received client requests, identifying features in the headers and client IP, EdgeOne also provides an active detection bot identification method. Active detection can perform Cookie verification and session tracking on the client, as well as client behavior verification for interaction, and further identify whether the current visitor is a tool based on the client's interaction feedback.

When you need to customize fine-grained policies for specific bot behaviors or features based on existing Bot management policies, custom bot rules can provide you with flexible matching conditions (such as client IP, header information, request method, static feature recognition, and client reputation analysis results), and can be combined with disposal strategies that randomly select actions by weight, helping you create accurate management strategies to effectively manage the risks brought by bot access to the site.

Bot Intelligent Analysis is suitable for situations where rapid deployment, identification, and analysis of website traffic patterns are needed. Bot Intelligent Analysis is based on a clustering analysis algorithm and a big data model intelligent engine, aiming to help you comprehensively judge the risk of requests from multiple perspectives and more conveniently use Bot management to quickly identify and deal with known or unknown bots, avoiding fixed single strategies being bypassed.

When Origin Protection is enabled, EdgeOne notifies you of the latest update of intermediate IPs of L4 proxy and site acceleration. You can sync them to the firewall rules of your origin, allowing only traffic from these IPs to your origin.

Image processing is to resize and convert images. The process of processing, caching and responding is taken place on EdgeOne servers. Your own origin only needs to store the original images, thus reducing image management costs on your side. EdgeOne can also compress images to improve page load speed without sacrificing visual impact.