EdgeNext Documentation

Configuration Scenario

EdgeNext CDN supports adding and modifying custom HTTP origin request headers.

Configuration Guide

View Configuration

Log in to the CDN console. From the menu, select Configuration → Domain Config, then click Details in the Actions column for the target domain. On the domain configuration page, under Origin (second section), you will find the Custom Request Header to Origin setting. It is empty by default:

Header Setting Types

Type	Description
Overwrite	Sets the specified origin request header. If the header does not exist, it is added. If the header already exists, the new value replaces the existing one (only one instance remains).
Add	Appends the specified origin request header. If the header already exists, the existing header is preserved and no duplicate is added.

Header Parameters

Header	Description
Custom Header	Custom header key: 1–100 characters, consisting of digits (0–9), letters (a–z, A–Z), and hyphens (-).Header value: 1–1000 characters. Chinese characters are not supported.

Notes:

• Headers apply to all files. Custom scoping is not currently supported.

Configuration Example

Suppose acceleration domain test.EdgeNext.com has the following origin request header configuration:

When a user requests http://test.EdgeNext.com/test/test.mp4:

1. For the host header (Add mode): If a host header already exists in the origin request, no change is made. If no host header exists, a host: test header is added.
2. For the x-cdn header (Overwrite mode): If an x-cdn header exists, it is replaced with the new value. If no x-cdn header exists, an x-cdn: BS header is added.