Origin rules

Updated at:

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

Custom origin Host

When Edge Security Acceleration (ESA) requests resources from an origin server, the default Host request header is determined by the origin server type. When needed, you can modify the origin Host request header to ensure that requests are correctly routed to the origin server.

Origin protocol and port

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 for requests that match specific characteristics.

Origin SNI

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.

DNS records

When resources under a single URI are stored on multiple origin servers, you can create a DNS rule to override the hostname's DNS record and route each request to the correct origin server.

Byte-range segment

With byte-range segments, Edge Security Acceleration (ESA) POPs include Range headers in back-to-origin requests so the origin server returns only the requested byte range to the ESA POP. This improves distribution efficiency, increases cache hit ratios, reduces back-to-origin traffic and the load on the origin server, and accelerates resource responses.

Origin HTTP request timeout

A well-tuned origin request timeout balances response efficiency against connection usage. Too short a timeout causes frequent fetch failures during network fluctuations; too long a timeout ties up connections when the origin is slow or unresponsive, blocking normal request handling.

Configure 301/302 redirect

When the origin returns a 301 or 302 redirect, ESA POPs follow the redirect to fetch the target resource directly, reducing round trips and accelerating delivery.

Availability

Origin rule

Free Edition

Basic Edition

Standard Edition

Premium Edition

Enterprise Edition

Number of rules

5

10

50

75

125

Custom origin Host

Supported

Supported

Supported

Supported

Supported

Origin protocol and port

Supported

Supported

Supported

Supported

Supported

Origin SNI

Supported

Supported

Supported

Supported

Supported

DNS records

Supported

Supported

Supported

Supported

Supported

Byte-range segment

Supported

Supported

Supported

Supported

Supported

Origin HTTP request timeout

Supported

Supported

Supported

Supported

Supported

Configure 301/302 redirect

Supported

Supported

Supported

Supported

Supported