Edge Acceleration

Site Acceleration
- Overview
- Quickly Import and Export Site Configuration
- Access Control
  - Token Authentication
  - Authentication Method A
  - Authentication Method B
  - Authentication Method C
  - Authentication Method D
  - Authentication Method V
- 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
  - 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
Edge DNS
- Overview
- Hosting DNS Records
  - Modifying DNS Servers
  - Configuring DNS Records
  - Batch Importing DNS Records
  - Advanced DNS Configuration
  - Enumeration of Resolution Lines and Corresponding Codes
- Domain Connection
  - Adding A Domain Name for Acceleration
  - Ownership Verification
  - Modifying CNAME Records
  - Verify Business Access
- 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
    - 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
  - 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

Origin-Pull Timeout

Overview
The EdgeOne rule engine supports setting custom origin-pull timeouts. You can reasonably set the origin-pull request timeout based on the network link conditions and the data processing capability of the origin server, to ensure normal origin-pull for the request. The origin-pull timeout is defined as follows. If there is no data response from the origin server after a node initiates an origin-pull request, no matter how long the duration is, the node will consider it a timeout and actively disconnect from the origin server.
Currently, it supports configuring the HTTP response timeout (please stay tuned to the support for TCP connection timeout configuration, which is coming soon). The timeout can be set to an integer from 5 to 600, with a default value of 15. It means that after a node is connected to an origin server and initiates an HTTP request, if the origin server does not respond with any data within 15 seconds (including scenarios where there is no data response at all or partial data response is interrupted), the node will consider it an HTTP response timeout,and will respond to the client with a 524 status code.
Note:
This timeout does not apply to HTTP/2 origin-pull. In the HTTP/2 origin-pull scenario, if no frames are sent/received within 600s (adjustment not supported yet), the connection will timeout and disconnect, and the requests on the connection will also disconnect synchronously.
﻿
Scenario: Configuring the HTTP Response Timeout to 60 Seconds
If the origin server for your business at the www.example.com domain name under the example.com site is heavily loaded and takes longer processing time, you should extend the timeout to 60 seconds, to avoid access failure due to active disconnection of the node after the default HTTP timeout of 15 seconds. You can refer to the following steps:
1. Log in to the EdgeOne console, click Site List in the left sidebar, and then click the site you want to configure in the site list.
2. On the site details page, click Site Acceleration to enter the global configuration page. Then click the Rule Engine tab.
3. On the rule engine page, click Create rule and select Add blank rule.
4. On the rule editing page, select the matching type as HOST and set its value to equal www.example.com.
5. Click the choice box below Action and select the action as Upstream Timeout in the pop-up action list. Then configure the HTTP response timeout to 60 seconds.
6. The complete rule configuration is shown below. Click Save and publish to finish the rule configuration.
﻿
﻿

Overview
Scenario: Configuring the HTTP Response Timeout to 60 Seconds