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

Client IP Geographical Location

Overview
If you need to collect the client geo location information within the origin for responding with different content based on the client geo location and analyzing regional distribution of users, you can set a custom origin-pull request header that carries the client IP geo location information back to the business origin.
Note:
The client IP geo location header is currently displayed at the country/region level. Its value is a two-letter country/region code. For details, see ISO 3166-1 alpha-2.
IPv6 address resolution is not currently supported.
For default headers carried in EdgeOne origin-pull requests, see Default HTTP Origin-Pull Request Headers. For modification of the origin-pull request header, see Modifying HTTP Origin-Pull Request Headers.
Directions
Scenario 1: Origin-Pull Request Headers Carrying the Client Geo Location Information for All Domain Names of the Site
If you need to set a custom origin-pull request header carrying the client geo location information for the entire access site, you can follow the steps below:
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 Site Acceleration to enter the global site configuration page. Then click Network Optimization in the right sidebar.
3. Locate the client IP geo location configuration card. This feature is disabled by default. Toggle the switch to enable it.
﻿
4. In the pop-up window, set a custom header name such as EO-Client-IPCountry and click Save.
Scenario 2: Origin-Pull Request Headers Carrying the Client Geo Location Information for a Specified Domain Name
If you need to set a custom origin-pull request header carrying the client geo location information only for a specified domain name, you can follow the steps below:
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 Site Acceleration to enter the global site configuration page. Then click the Rule Engine tab.
3. On the rule engine management page, click Create rule and select Add blank rule.
4. On the rule editing page, select the matching type as HOST to match requests for the specified domain name.
5. Click Action > choice box and select the action as Client IP location Header in the dropdown action list. Toggle the switch to enable it and enter a header name such as EO-Client-IPCountry.
﻿
6. Click Save and Publish to complete the rule configuration.
﻿

Overview
Directions
- Scenario 1: Origin-Pull Request Headers Carrying the Client Geo Location Information for All Domain Names of the Site
- Scenario 2: Origin-Pull Request Headers Carrying the Client Geo Location Information for a Specified Domain Name