Overview

This section contains introductions for self-serviceable functions including origin servers, origin request protocol, origin port, origin host, origin SNI, HTTP request headers, origin URI overriding, 302/301 request following, origin request to private bucket,origin request query strings overriding. In addition, some others functinos can only be configured from backend team including HTTP response headers, origin request based on IPv4/IPv6, origin request based on ISP/regions, Common Name Whitelist, advanced origin request settings and origin request timeout settings, you will have to submit a ticket to the eSurfing Cloud technical support team for setting them up.

Configuration Page Overview

Function Brief Intro

The following table describes the available functions when CDN retrieves contents from your origin servers.

Feature	Description
Configuring Origin Servers	IP addresses or domain names are supported. You can add up to 60 origin servers.
Configuring the Origin Protocol Policy	You can specify the request protocol when CDN fetches contents from your origin servers. The request protocol could be HTTP, HTTPS or just inherit or sustain the request protocol initiated by client.
Configuring the Origin Port	You can specify the service port which CDN send requests to origin servers.
Configuring an Origin Host	If one single origin IP address is associated with multiple hostnames at your origin, the origin host helps to clarify the target hostnames at your origin and get the. correct contents from origin.
Configuring origin Host for specific origin	If you have configured multiple origin addresses for one acceleration domain, you are allowed to setup different origin host for each origin address, so CDN will carry different host when retrieving contents from different origin.
Configuring origin request with SNI	If multiple acceleration domains are configured with identical origin IP address, and meanwile, the origin request protocol is set to HTTPS, you can enable origin request with SNI. This way, the origin server can return the correct SSL certificate of the specified domain name, thus achieving the purpose of multiple domain names sharing the same origin server.
Configuring HTTP request headers	You can add, modify, or delete HTTP request headers when CDN sends requests to origin.
Configuring HTTP response headers	Overriding the http response headers given by origin.
Configuring origin URI overriding	You can override the URI of the origin request URL.
Configuring 301/302request following	If the 301/302 request following feature is enabled, when CDN receives a 301 or 302 status code from an origin server, CDN server will send another request to obtain the contents specified in the Location header from the 301/302 response returned by the origin server previously, and eventually give the contents to clients instead of directly passing the 301/302 to clients.
Configuring origin request based on IPv4/IPv6	If a domain name is configured with IPv4 origin servers and IPv6 origin servers, you can enable origin request based on IPv4/IPv6 to match the IP version of the client when CDN sends requests to origin. Specifically, requests from IPv4 clients are forwarded to IPv4 origin servers, and requests from IPv6 clients are forwarded to IPv6 origin servers.
Configuring origin request based on region/ISP	If a domain name is configured with multiple origin servers, you can group origin servers by region or ISP to balance loads through CDN. After you configure this feature, client requests from different regions or ISPs are redirected to different origin servers. As a result, when a CDN POP retrieves resources from origin servers, the request will be send to origin servers within the same ISP or geographically nearest to the CDN POP.
Configuringquery strings overriding	You can rewrite the query strings in the origin request URL, i.e the arguments after the question mark (?) in the URL.
Common Name whitelist	After enabling the Common Name whitelist feature, when CDN nodes connect to the origin server through the HTTPS protocol, they will verify the SNI of the request and the Common Name of the certificate returned by the origin server.
Origin request to private bucket	If you use media storage (i.e., object storage (converged version)) as the origin server, you need to configure the origin request to private bucket feature after setting the new bucket permission as "Private".
Advanced origin rules	If you expect CDN to return to different origin servers based on some special scenarios, such as returning to different origin servers based on different file extensions or different paths in the request URL, you can set it up as you need.
Origin request timeout settings	The origin request timeout time refers to the maximum allowed time for CDN nodes to wait for a response from the origin server.

Content Delivery Network

Origin Configuration Overview