---
schema_version: "1"
id: 6919ee9abbffd73989501b1758ebdf41c9a344bdbcb9a6596a83dad6a6719958
title: Configure Proxy Zone Settings
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_legacy_configure_proxy_zone_settings.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_legacy_configure_proxy_zone_settings.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a5ab789c1c9e8c8cb2048bc03ce14c2bdc4e78816d32380c78b71a528ab87251
description: After you migrate a B2C Commerce legacy zone to a proxy zone, most settings transfer automatically. Manually copy the two settings that don't transfer, Logpush and rate limiting rules, from the legacy zone to the new proxy zone.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Configure Proxy Zone Settings

After you migrate a B2C Commerce legacy zone to a proxy zone, most settings transfer automatically. Manually copy the two settings that don't transfer, Logpush and rate limiting rules, from the legacy zone to the new proxy zone.

[Which Salesforce Commerce Product Do I Have?](https://help.salesforce.com/s/articleView?id=commerce.comm_what_product.htm&language=en_US)

When you migrate a legacy zone to a proxy zone, most zone settings are transferred automatically. Two settings aren't, so copy each one manually from the legacy zone to the proxy zone: the Logpush configuration and the rate limiting rules. This task is part of the migration sequence. See [Proxy Zone Migration Overview](https://help.salesforce.com/s/articleView?id=cc.b2c_migrating_proxy_zones.htm&release=264.0.0&type=5 "Migrate legacy zones to proxy zones by using B2C Commerce Business Manager or the CDN-API. Proxy zones give you standard eCDN configuration and the latest security features, and they prevent common hierarchy-assignment issues. Migration is required to move to Hyperforce, which doesn't support legacy zones.").

1. In Business Manager, click the 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. Copy the Logpush settings from the legacy zone to the proxy zone.
    1. In the legacy zone you migrated, select **Settings** | **Logpush**.
    2. Select and copy the Logpush setting.
    3. In the new proxy zone, select **Settings** | **Logpush**.
    4. Paste the Logpush setting.
    5. Validate bucket ownership using the CDN-API. See [eCDN Logpush](https://developer.salesforce.com/docs/commerce/commerce-api/guide/cdn-zones-logpush.html).
3. Copy the rate limiting rules from the legacy zone to the proxy zone by using the CDN-API.
    1. Retrieve the rate limiting rules from the legacy zone.
    2. Create the same rate limiting rules on the new proxy zone. See [eCDN Rate Limiting Rules](https://developer.salesforce.com/docs/commerce/commerce-api/guide/cdn-rate-limiting-rules.html).

Continue with [Create a Custom Hostname with a Custom Certificate](https://help.salesforce.com/s/articleView?id=cc.b2c_legacy_create_custom_hostname_with_custom_cert.htm&release=264.0.0&type=5 "When you migrate a legacy zone to a proxy zone, a certificate is automatically created with the validation method set to \"http\". If you need a different validation method, delete the generated certificate and add a custom one. Create the custom certificate in Business Manager for B2C Commerce or use the addCertificateForZone API.").