Edge Security Acceleration:Origin rules

Feature overview

You can configure origin rules for features as followed:

• Origin host

  By default, the domain name in a client request is used as the Host request header when Edge Security Acceleration (ESA) requests resources from the origin server. If you configure an origin domain that is different from the requested domain name, you need to modify the origin host to ensure that origin fetch requests go to the correct origin.

• Origin protocol and port

  By default, ESA points of presence (POPs) retrieve content from origin servers using the same protocol as the client. You can create origin rules to configure different protocols and ports, and apply the rules to origin requests that have different characteristics.

• Origin SNI

  If multiple websites are hosted on a single server with the same IP address, you must specify the SNI when POPs retrieve content from the origin server over HTTPS. The origin server returns the Secure Sockets Layer (SSL) certificate of the desired domain name based on the configured SNI to ensure the correct resources are returned.

• DNS records

  If you specify a Uniform Resource Identifier (URI) but the requested resources are stored on different origin servers, you can create a DNS rule to replace the DNS record resolved from the hostname in the request. This ensures that the request is routed to the correct server to obtain the desired resources.

• Range sharding

  Range requests refer to origin requests that include the Range header. When an origin server receives a range request, it immediately serves the requested range from the cache if ESA cache contains the requested range. Range requests speed up file distribution, increase cache hit ratios, boost resource response times, and reduce origin traffic.

• Origin HTTP request timeout

  Setting an appropriate timeout period for HTTP requests to the origin server enhances response efficiency. If the timeout period is too short, network fluctuations can lead to frequent fetch failures from the origin. If it is too long, it may tie up too many connections when the origin is overloaded or unresponsive, disrupting the handling of regular requests.

• Configure 301/302 redirect follow

  The 301/302 redirect follow feature supports HTTP 301 and 302 status codes from the origin server. ESA POPs handle these status codes on behalf of users, reducing data interactions and speeding up resource fetch.

Availability