---
schema_version: "1"
id: 16f0ddf7c532eb33c005b7dcfa501969955543b89a66a891e60f81281fcf69bb
title: Configure a Host Header Override Rule for an eCDN Zone
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_eCDN_configure_host_header_override.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_eCDN_configure_host_header_override.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5a0d8de2a0291b1b8e93994091416ac426e293f1359a207dcab087c4e9783427
description: To support a single hostname across multiple realms, create a Host Header Override Rule for B2C Commerce sites that use an external content delivery network (CDN). This rule replaces unique hostnames with a common hostname to maintain the single-hostname setup. If you reuse a hostname, traffic can be unintentionally served from a different realm.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Configure a Host Header Override Rule for an eCDN Zone

To support a single hostname across multiple realms, create a Host Header Override Rule for B2C Commerce sites that use an external content delivery network (CDN). This rule replaces unique hostnames with a common hostname to maintain the single-hostname setup. If you reuse a hostname, traffic can be unintentionally served from a different realm.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note Host Header Override isn't available on SCAPI zones. See [SCAPI Zone Support for B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_scapi_zone.htm&release=264.0.0&type=5 "A SCAPI zone is the Salesforce-managed eCDN zone that fronts Salesforce Commerce API (SCAPI) traffic. Starting with B2C Commerce 26.10, the Production instance includes a subset of eCDN security controls and analytics for this zone in Business Manager and the CDN API, with no support case required.").

Use host header override rules when your origin expects a different host value than the shopper-facing hostname. This setup is common for customers using stacked CDNs or custom origin-routing patterns.

Proxy zones don’t support the same subdomain/hostname across zones, so a unique hostname is required in each zone with the appropriate custom hostname and certificate.

Before you create a host header override rule, make sure that you have your own stacked CDN configuration. CDN stacking is a prerequisite for directing traffic to appropriate eCDN zones based on locales or regions.

The Host Header Override Rules tab is part of the Configure Zone screen; for the full set of zone security controls, see [eCDN Zone Security Rules](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_security_rules.htm&release=264.0.0&type=5 "Use the Security Rules tab on the Configure Zone screen to protect a B2C Commerce embedded CDN (eCDN) zone with web application firewall (WAF) managed rulesets, realm and zone security rules, custom firewall rules, and rate limiting. Learn what each control does, which zone types are eligible, and how traffic from trusted sources bypasses security checks.").

Create host header rules for each locale. To create a host header override rule:

1. In Business Manager, click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **Administration** | **Sites** | **Embedded CDN Settings**.
2. Locate the zone you want to configure, and select **Configure Zone** from the dropdown menu.
    
    ![Configure Zone dropdown menu for a Proxy Zone in Business Manager](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_configure_zone.png)
3. Select the Host Header Override Rules tab, and then select **New Rule**. To switch to a different zone from this tab, select another name from the Zone dropdown menu.
4. Enter the Host Header Override Rule details:
    1. Enter the rule expression using the visual dropdown interface to select a field, operator, and value. This expression specifies the host header of incoming requests where the traffic goes. For example, `Hostname equals shop.alpine.net`.
    2. (Optional) If you want the rule to be active when you save it, select **Enable Host Header Override Rule Upon Saving**. If you’re not ready to activate the rule yet, create it first. When you’re ready, return to the Host Header Override Rules tab and enable your rule from the list.
    3. The Rule Name is automatically filled based on the rule details.
    4. Click **Save**. Upon saving, a check makes sure that the rule’s host header ends with the same hostname as the current zone.
5. Modify your external CDN to route traffic to the proxy zones for each locale.