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

このページは現在英語版のみで提供されており、日本語版も近日中に提供される予定です。ご利用いただきありがとうございます。

Viewing the Health Status of Origin Server

The node probe results will display the outcomes of probes initiated by EdgeOne from various nodes and regions within the global availability zones towards the current origin group. Users can view these probe results to find whether the origin is healthy across different zones.
Note:
EdgeOne Load Balancing feature is in beta testing. If you want to use it, you can Contact Us.
1. Log in to the EdgeOne console. In the left menu bar, click the Site List. Within this list, click the Site need to be configured to go to the details page.
2. On the site details page, click Origin Settings > Load Balancing.
3. On the Load Balancing  page, click the desired Load balancer.
﻿
4. In the instance details page, click View details.
﻿
5. In the node probe results, nodes are differentiated by the following three colors:
Green Node: Indicates that the probe node in the region has considered all origins in the origin group to be healthy.
Red Node: Indicates that the probe node in the region has considered one or more origins in the origin group to be unhealthy.
Gray Node: Indicates that the probe node in the region cannot probe any origins. Probing is done at the IP level, meaning if the origin is a domain, the domain will be resolved into an IP before it probes. This situation usually occurs if you have entered an incorrect domain origin which cannot be resolved into an IP. In this case, it is recommended to check for potential spelling mistakes in the origin domain or whether the corresponding domain has expired.
﻿
Note:
Probe nodes in different regions make independent decisions. Edge nodes will route requests back to the origin based on the probe results from the nearest probe nodes in each region.
For example: If your origin is in Hong Kong (China), and the probe node in Singapore considers the origin to be unhealthy whereas the probe node in Germany considers it to be healthy, traffic from the Singapore region will not be routed to that origin, while traffic from the Germany region will continue to be directed to that origin.
In the scenario described above, you can refer to the probe results from other regions for a comprehensive view. If only a few nodes consider the origin to be unhealthy, it might be due to network fluctuations in certain areas. If the majority of nodes consider the origin to be unhealthy, it is recommended to check whether the origin has malfunctioned.
﻿
﻿