请选择
Edge Acceleration
  • Site Acceleration
    • Overview
    • Access Control
      • Token Authentication
    • 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
  • Smart Acceleration
  • 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
      • 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-pull configuration
        • Configuring Origin-Pull HTTPS
        • Host Header Rewrite
        • Controlling Origin-pull Requests
        • Redirect Following During Origin-Pull
        • HTTP/2 Origin-Pull
        • Range GETs
      • Related References
        • ld Version Origin Group Compatible Related Issues
        • VOD Origin Server Details
      • 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
  • Image Processing
Docs Overview/
Edge Acceleration/
Site Acceleration/
Request and Response Actions/
Default HTTP Headers of Origin-Pull Requests/

Default HTTP Headers of Origin-Pull Requests

Overview

EdgeOne passes through all client request headers to the origin, and the origin-pull request carries the default custom request headers of EdgeOne. To modify the HTTP headers of origin-pull requests, see Modifying HTTP Headers of Origin-Pull Requests.




Default HTTP headers of origin-pull requests

EdgeOne adds the following default HTTP headers to origin-pull requests.

EO-Connecting-IP

The EO-Connecting-IP header records the IP that of the request initiator. If the request is not forwarded by any proxy, the IP address in the header is the real IP address of the client. Otherwise, it’s the proxy IP.

X-Forwarded-For

This header records the proxy IP and real client IP. If a client request is forwarded to an EdgeOne node after multiple hops, the header records the real client IP and the IP of proxy before the EdgeOne node. The value of the header is determined based on the following rules:
If a request sent to an EdgeOne node carries the X-Forwarded-For header that has recorded the client IP address, EdgeOne appends the IP address of the proxy before the EdgeOne node to the header. For example, if the client request carries X-Forwarded-For: 192.168.1.1 (where 192.168.1.1 is the client IP) and is forwarded to an EdgeOne node via the proxy 10.1.1.1, the header of the origin-pull request is X-Forwarded-For: 192.168.1.1,10.1.1.1.
If the request does not carry the X-Forwarded-For header, EdgeOne adds this header to the origin-pull request, taking the proxy IP of the EdgeOne node as the value. In this case, it’s the same as the EO-Connecting-IP header.
For more information, see X-Forwarded-For.

X-Forwarded-Proto

The X-Forwarded-Proto header records the HTTP protocol used by the client to initiate the request. Valid values:
X-Forwarded-Proto: http
X-Forwarded-Proto: https
X-Forwarded-Proto: quic
For more information, see X-Forwarded-Proto.

CDN-Loop

It records how many times a client request passes an EdgeOne node. The count is added by one every time the request passes the node. When the count reaches 16, the EdgeOne node denies the request and returns the 423 status code.

Example: CDN-Loop: TencentEdgeOne; loops=3.

EO-LOG-UUID

It carries the unique identifier of the request. When an access exception occurs, you can locate the problem by querying logs with this UID.

Example: EO-LOG-UUID: 4105283880544427145.