All pages
Powered by GitBook
1 of 1

Loading...

Origin Host Header

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

The Origin Host Header feature allows you to define a custom domain to be sent in the Host header of requests forwarded to your origin. Many origin servers rely on the Host header for routing, virtual hosting, or tenant identification. When this option is enabled and a domain is provided, the CDN replaces the default host value with the one you specify.

The feature does not modify viewer-facing responses and does not affect caching behavior.

How Origin Host Header Works

You can configure X-CDN Header in the Medianova Control Panel or via

When the feature is active:

  • The CDN overwrites the Host header in the origin request with the domain you provide.

  • The domain must be entered without http:// or https://.

  • The configured value is applied to all origin fetches for the selected CDN Resource.

The purpose of this feature is to ensure compatibility with origins that require a specific hostname, especially in environments where multiple sites share the same origin infrastructure.

Use Cases

Virtual hosting environments

Ensure the correct site is selected when multiple hostnames share the same origin.

Multi-tenant systems

Send a tenant-specific domain in the Host header for proper routing.

Origin behavior validation

Match the exact hostname your origin expects for SSL/SNI evaluation or application routing logic (when applicable to host header usage).

Notes

  • Enter only the domain name (e.g., subdomain.example.com).

  • Do not include URL schemes such as http:// or https://.

  • This feature modifies only the origin-bound request and does not impact the viewer response.

The behavior supports any valid domain that your origin server expects for routing or validation.

Incorrect domain entries may cause the origin to respond with errors or unexpected routing behavior.

API
Origin Host Header field enabled with sample domain