Advanced Origin Settings

Define advanced origin routing rules by matching requests to specific origins based on URI patterns, protocols, domains, ports, and priority.

Advanced Origin Settings allow you to configure granular origin-routing behavior for specific URIs, file types, or directories. By defining rule-based conditions, you can route selected traffic to different origins, override ports, set custom host headers, or assign priorities for complex routing environments.

You can manage Advanced Origin Settings in the Medianova Control Panel or via API.

Log in to the Medianova Control Panel, select a CDN resource in the CDN section, and navigate to the Origin Settings tab.

Advanced Origin Settings use rule-based logic. Each rule defines what request pattern to match and how the CDN should route that traffic.

Add an Origin Rule

This workflow creates a new rule for routing selected requests to a specific origin configuration.

1

Open the Add Rule Dialog

Select Add in the Advanced Origin Settings section to create a new routing rule.

2

Select the URI Match Mode

Choose whether the rule should match an Exact Path, Prefix, File Extension, or Regex pattern.

3

Define the URI Match Rule

Enter the URI, directory, extension, or expression that determines which requests will use this origin rule.

4

Select the Protocol

Choose whether the CDN forwards requests using HTTP, HTTPS, or Same as Request.

5

Enter the Domain or IP

Specify the origin host that the CDN should forward matched traffic to.

6

Configure HTTP and HTTPS Ports

Enter the port numbers the CDN should use when communicating with the origin.

7

Set the Host Header

Define a custom Host header if the origin requires a different hostname than the request URL.

8

Assign Priority

Choose a priority value to control which rule applies if multiple rules match the same request.

9

Save the Rule

Select Add to save the rule to the rule list.

10

Submit the Configuration

Click Submit to apply all rule changes to the CDN resource.

Edit an Origin Rule

1

Select the Rule To Edit

Choose an existing rule from the list in the Advanced Origin Settings section.

2

Modify the Required Fields

Update match conditions, origin host, ports, or priority values.

3

Save the Updated Rule

Click Submit to apply the updated configuration.

Delete an Origin Rule

1

Remove the Rule

Select the delete icon next to the rule you want to remove.

2

Confirm Deletion

Submit the change to finalize the removal.

Behaviour

Advanced Origin Settings follow a priority-based evaluation model:

• Highest priority wins. Lower numeric values represent higher priority.

• If multiple rules match the incoming request, the CDN applies the rule with the highest priority.

• If no rules match, the CDN uses the default origin configuration.

Routing decisions consider:

• URI match pattern

• Origin protocol selection

• Domain/IP

• Ports

• Host header

This allows precise routing for APIs, media directories, file extensions, or multi-origin deployments.

FAQ

What happens if multiple rules match the same request?

The rule with the highest priority (lowest priority number) is applied.

Do regex or prefix rules impact performance?

Regex rules are more expensive than prefix or extension matches. Use them only when necessary.

What if no Advanced Origin rule matches the request?

The request is sent to the default origin defined in the main Origin Settings section.