Origin rules let you configure origin hosts, ports, protocols, SNI, DNS records, and byte-range segments for specific requests.
Supported configurations
Configure origin rules for specific requests:
|
Configuration |
Description |
|
By default, Edge Security Acceleration (ESA) uses the domain name from a client request as the Host request header when it requests resources from the origin server. If your origin domain differs from the requested domain name, you must modify the origin host to ensure that origin fetch requests are routed to the correct origin. |
|
|
By default, Edge Security Acceleration (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. |
|
|
If multiple domain names are bound to the same origin IP address, you must specify the domain name to be accessed (the origin SNI) when a point of presence (POP) accesses the origin server over HTTPS. The origin server then returns the SSL certificate for the corresponding domain name based on the SNI to ensure a successful origin fetch. |
|
|
If you use a single URI for resources stored on multiple origin servers, you can create a DNS rule to override the DNS record resolved from the request's hostname, routing requests to the correct origin server. |
|
|
Byte-range segments allow Edge Security Acceleration (ESA) points of presence (POPs) to include Range information in back-to-origin HTTP requests. When an origin server receives such a request, it returns only the specified byte range of content to the ESA POP. Byte-range segments improve file distribution efficiency, increase the cache hit ratio, reduce back-to-origin traffic and the load on the origin server, and accelerate resource responses. |
|
|
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. |
|
|
The 301/302 redirect follow feature supports HTTP 301 and 302 status codes from the origin server. Edge Security Acceleration (ESA) points of presence (POPs) handle these status codes on behalf of users, reducing data interactions and speeding up resource fetch. |
Availability
|
Origin rule |
Free Edition |
Basic Edition |
Standard Edition |
Premium Edition |
Enterprise Edition |
|
Number of rules |
5 |
10 |
50 |
75 |
125 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Supported |
|
|
|
|
|
|
Supported |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|