> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/headers/origin-host-header.md).

# Origin Host Header

Learn how to configure a custom Host header for origin requests in the Medianova Control Panel.

**Origin Host Header** allows you to specify the hostname sent in the `Host` header of origin requests. When enabled, the CDN replaces the default `Host` header value with the configured domain.

This is commonly required when multiple websites or applications share the same origin infrastructure and the origin uses the `Host` header to route requests to the correct virtual host.

You can configure Origin Host Header in the [Medianova Control Panel](https://cloud.medianova.com) or via the [API](https://clients.medianova.com/api-documentation/performance-cdn/headers#put-api-v1-cdn-organization_uuid-resource-resource_uuid-3).

## Configure Origin Host Header

{% stepper %}
{% step %}

### Open Origin Host Header

Open your CDN Resource and select **Headers**.

Locate the **Origin Host Header** section.
{% endstep %}

{% step %}

### Enable Origin Host Header

Enable **Origin Host Header**.
{% endstep %}

{% step %}

### Enter the Host Domain

Enter the domain that the CDN should send in the `Host` header under **Host domain**.

Enter the domain without a URL scheme.

For example:

```
origin.example.com
```

Do not enter:

```
https://origin.example.com
```

{% hint style="warning" %}
The configured domain must match a hostname recognized by your origin. An incorrect value can cause the origin to route the request incorrectly or return an unexpected response.
{% endhint %}
{% endstep %}

{% step %}

### Save the Configuration

Click **Save** in the pending changes bar.

Review the pending changes and confirm the update.
{% endstep %}
{% endstepper %}

## How Origin Host Header Works

When Origin Host Header is enabled, the CDN replaces the default `Host` header in requests sent to the origin with the configured **Host domain**.

For example, if the configured value is:

```
origin.example.com
```

the origin request includes:

```http
Host: origin.example.com
```

This allows origins that use name-based virtual hosting or Host-based application routing to process the request using the expected hostname.

{% hint style="info" %}
Origin Host Header controls the HTTP `Host` header sent to the origin. For the server name used during the TLS handshake with an HTTPS origin, configure **Origin SNI Request** separately.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/headers/origin-host-header.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.