Edge Acceleration

Site Acceleration
- Overview
- Access Control
  - Token authentication
    - Token Authentication
    - Authentication Method A
    - Authentication Method B
    - Authentication Method C
    - Authentication Method D
    - Authentication Method V
- Smart Acceleration
- Cache configuration
  - Overview
  - EdgeOne caching rules introduction
    - 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
    - Prefetch M3U8
  - How to improve the Cache Hit Rate of EdgeOne
- File Optimization
  - Content Compression
  - 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
  - Network Error Logging
- URL Rewrite
  - Access URL Redirection
  - Origin-Pull URL Rewrite
- Modifying Header
  - Modifying HTTP Response Headers
  - Modifying HTTP Request Headers
- Modify response content
  - HTTP Response
  - Custom Error Page
- Rules Engine
  - Overview
  - Rule Management
  - variables
  - Supported Matching Types and Actions
- Image and video processing
  - Audio and Video Pre-pulling
  - Just-in-Time Image Processing
  - Video Just-In-Time Processing
  - VOD Media Origin
- Speed limit for single connection download
- Request and Response Actions
  - HTTP Response
  - Processing order
  - Default HTTP Headers of Origin-Pull Requests
  - Default HTTP Response Headers
  - HTTP Restrictions
- 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
Domain name service and origin server configuration
- Domain Name Services
  - Overview
  - DNS resolution for managed domains
    - Modifying DNS Servers
    - Configuring DNS Records
    - Batch Importing DNS Records
    - Advanced DNS Configuration
  - Access accelerated domains
    - Adding A Domain Name for Acceleration
    - Ownership Verification
    - Modifying CNAME Records
    - Verify Business Access
  - Traffic scheduling
    - Traffic Scheduling Management
- HTTPS Certificate
  - Overview
  - Edge HTTPS Certificate
    - Overview
    - Deploying/Updating SSL Certificate for A Domain Name
    - Configuring A Free Certificate for A Domain Name
    - Using Keyless Certificate
  - Edge mTLS Authentication
  - Origin Certificate Validation
  - HTTPS configuration
    - Forced HTTPS Access
    - Enabling HSTS
    - SSL/TLS security configuration
      - Configuring SSL/TLS Security
      - TLS Versions and Cipher Suites
    - Enabling OCSP Stapling
  - Related References
    - Using OpenSSL to Generate Self-Signed Certificates
    - Certificate Format Requirements
    - The Difference Between one-way authentication and Mutual authentication
- 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 configuration
    - Origin-Pull Timeout
    - Configuring Origin-Pull HTTPS
    - Host Header Rewrite
    - Controlling Origin-pull Requests
    - Redirect Following During Origin-Pull
    - HTTP/2 Origin-Pull
    - Range GETs
    - Modify Origin
    - Origin-pull Rate Limiting Policy
  - Origin Protection(Obtaining/Updating Origin IP Address Range)
  - Related References
    - ld Version Origin Group Compatible Related Issues

Batch Importing DNS Records

If your site needs to access EdgeOne using the NS mode, it is recommended to add the currently effective DNS records by batch importing before modifying the DNS server, to avoid interruptions in the current DNS resolution service.
Note:
Up to 100 records can be imported at a time. If there are many records, it is recommended to import them in batches.
The current import source supports Tencent Cloud DNSPod, Alibaba Cloud DNS, and CloudFlare. If your current DNS resolution is not hosted on these service providers or if the format has an error when EdgeOne resolves the DNS records of these providers (as the record formats of different providers may change at any time), it is recommended to use the template import method.
Scenario 1: Batch Importing DNS Records During Site Access
Sample Scenario
At present, example.com is added and needs to be accessed using NS. The current DNS resolution is hosted on Alibaba Cloud DNS, and the existing DNS records need to be batch imported to EdgeOne.
Directions
1. Log in to the EdgeOne console and click Add site in the upper right corner on the service overview page.
2. Refer to Quick Start to complete Steps 1 and 2 of creating a site.
3. In Step 3, select the access mode as NS and click Batch import.
4. Select the import source, such as Alibaba Cloud DNS in this scenario. Then select the DNS record files exported from Alibaba Cloud DNS. For the export method, refer to the product documentation of the corresponding provider.
﻿
5. Click Next to identify the content of the imported file. If the file format is checked to be correct, you should further confirm the DNS record content to be imported. If the DNS record content has an error, you can modify it on this page.
6. After confirming no errors, click Import and wait for background import to complete.
Scenario 2: Batch Importing DNS Records on the Domain Name Management Page
Sample Scenario
At present, a site example.com exists and uses the NS access mode. Multiple DNS resolution records need to be batch added.
Directions
1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the site details page, click Domain Name Service > DNS Records.
3. Click Batch import, select the batch import source as Template import, and download the corresponding template. Four file formats are supported, including csv templates, xlsx spreadsheets, txt files, and zone files.
4. Fill in the DNS records according to the template format and save the file. You can select the completed import template by selecting a file or dragging it directly into the console.
5. Click Next to identify the template content. If the file format is checked to be correct, you should further confirm the DNS record content to be imported. If the DNS record content has an error, you can modify it on this page.
﻿
6. After confirming no errors, click Import and wait for background import to complete.
﻿

Scenario 1: Batch Importing DNS Records During Site Access
- Sample Scenario
- Directions
Scenario 2: Batch Importing DNS Records on the Domain Name Management Page
- Sample Scenario
- Directions