Origin Rules (beta)
Origin Rules allow you to customize where the incoming traffic will go and with which parameters. Currently you can perform the following overrides:
- Host header override: Overrides the
Hostheader of incoming requests. - Resolve override: Overrides the resolved hostname of incoming requests.
- Destination port override: Overrides the resolved destination port of incoming requests.
- SNI override: Overrides the Server Name Indication (SNI) value of incoming requests.
The Origin Rule expression will determine when these overrides are applied.
Availability
| Free | Pro | Business | Enterprise | |
|---|---|---|---|---|
| Number of Origin Rules | 10 | 20 | 50 | 100 |
| Host header override | — | — | — | Yes |
| Resolve override | — | — | — | Yes |
| SNI override | — | — | — | Yes |
| Destination port override | Yes | Yes | Yes | Yes |
Important remarks
If you override the hostname with an Origin Rule (via Host header override or resolve override) and add a header override to your load balancer configuration, the Origin Rule will take precedence over the load balancer configuration.
Unlike Page Rules, an Origin Rule performing a Host header override will not automatically update the SNI value of the original request. To also change the SNI value, add an SNI override in the same Origin Rule or create a separate Origin Rule for this purpose.