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

Overview

After your site is connected to EdgeOne, EdgeOne edge nodes will decide whether to cache the resource files of the client request response based on the cache configuration rules. After the edge node caches the file, when other users initiate the same file request, it can be directly responded by the EdgeOne edge node, effectively avoiding the long link origin-pull situation and responding to the latest file request at a faster speed.
﻿
You can customize your site cache according to the following usage scenarios:
Rule Type
Usage Scenario
Function
Custom EdgeOne node caching rules
There are various types of file resources under the site/domain, and it is necessary to customize the caching time of various resources in the node to ensure that users access the latest files while reducing the origin-pull request volume;
The site/domain contains dynamic resources, and it is necessary to avoid caching the content of these resources.
﻿EdgeOne Node Cache TTL﻿
﻿
When requesting the same path file, different URLs carry different parameters, request headers, etc., which will point to different files;
When requesting the same path file, the parameters, request headers, etc. carried by the URL do not affect the file version and need to point to the same cache file.
﻿Custom Cache Key﻿
ache control when origin response exception
When the origin response is abnormal, it is necessary to protect the origin from further damage while normally responding to customer requests.
﻿Status code caching TTL﻿
﻿Offline Caching﻿
Control browser caching
To further improve the web page loading speed and reduce traffic consumption, allow the browser to cache static resources files for a certain period of time.
﻿Browser Cache TTL﻿
Clear the cache
When the cached files in the node have expired or illegal resources are cached, clear the cached resources in the node.
﻿Cache Purge﻿
URL Pre-Warming
When the domain access is just completed or the files are updated, it is necessary to cache the files in advance to the EdgeOne node to improve the acceleration effect and reduce the origin-pull volume during peak periods.
﻿URL Pre-Warming﻿
Cache Prefresh
For files with continuous user access, it is necessary to ensure that the files have continuous cache in the node to avoid concentrated origin-pull after the cache expires. The cache pre-refresh can be used to verify the validity of the files and refresh the cache time.
﻿Cache Prefresh﻿
﻿
If you need to learn more about cache rules, you can refer to the following:
﻿Learn about EdgeOne's content caching rules﻿
﻿Learn about the role of Cache Key﻿
﻿Learn about the role of Vary feature﻿
﻿

Rule Type	Usage Scenario	Function
Custom EdgeOne node caching rules	There are various types of file resources under the site/domain, and it is necessary to customize the caching time of various resources in the node to ensure that users access the latest files while reducing the origin-pull request volume; The site/domain contains dynamic resources, and it is necessary to avoid caching the content of these resources.	EdgeOne Node Cache TTL
Custom EdgeOne node caching rules		When requesting the same path file, different URLs carry different parameters, request headers, etc., which will point to different files; When requesting the same path file, the parameters, request headers, etc. carried by the URL do not affect the file version and need to point to the same cache file.	Custom Cache Key
ache control when origin response exception	When the origin response is abnormal, it is necessary to protect the origin from further damage while normally responding to customer requests.	Status code caching TTL Offline Caching
Control browser caching	To further improve the web page loading speed and reduce traffic consumption, allow the browser to cache static resources files for a certain period of time.	Browser Cache TTL
Clear the cache	When the cached files in the node have expired or illegal resources are cached, clear the cached resources in the node.	Cache Purge
URL Pre-Warming	When the domain access is just completed or the files are updated, it is necessary to cache the files in advance to the EdgeOne node to improve the acceleration effect and reduce the origin-pull volume during peak periods.	URL Pre-Warming
Cache Prefresh	For files with continuous user access, it is necessary to ensure that the files have continuous cache in the node to avoid concentrated origin-pull after the cache expires. The cache pre-refresh can be used to verify the validity of the files and refresh the cache time.	Cache Prefresh