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

EdgeOne Load Balancing is ideal for scenarios where high availability of origins is crucial. It supports the configuration of 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 automatically switched to the secondary source to ensure business continuity.
Proactively Checking origin Health Status: Preemptively disables failed origins, and redirects business traffic to healthy origins. Prevents a situation where a significant number of legitimate service requests are still directed to malfunctioning 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 to preemptively 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.
﻿
More Information
﻿Quickly Create Load Balancers﻿
﻿Load Balancing-Related Concepts﻿
Health Check Policies
﻿

Use Cases
Supported Capabilities
More Information