All Products
Search
Document Center

Edge Security Acceleration:Configure the Common Name whitelist

Last Updated:Aug 26, 2026

The Common Name whitelist lets a DCDN node connect to an origin server over HTTPS when the Common Name of the origin server certificate does not match the Server Name Indication (SNI) in the client request. Add the domain name carried in the SNI to the whitelist so that the DCDN node can establish the HTTPS connection to the origin server.

How it works

A Common Name is the specific domain name for which an SSL certificate is requested. When a node connects to an origin server over HTTPS, the system validates the Server Name Indication (SNI) in the client request against the Common Name of the certificate returned by the origin server. As shown in the following figure, if the two values do not match, the request is rejected, and the DCDN node cannot establish a connection to the origin server over HTTPS. In this case, enable the Common Name whitelist feature and add domain2 to the whitelist so that the DCDN node can establish a connection to the origin server over HTTPS.

SNI and Common Name validation during HTTPS back-to-origin

Prerequisites

The Common Name whitelist is disabled by default. To enable it for a specific domain name, submit a ticket.

Procedure

  1. Log on to the DCDN console.

  2. In the left-side navigation pane, click Domain Names.

  3. On the Domain Names page, find the domain name that you want to manage and click Configure in the Actions column.

  4. In the left-side navigation tree of the domain name, click Origin Fetch.

  5. On the Origin Fetch tab, find the Common Name Whitelist section and turn on the Status switch.

  6. Enter the domain names that you want to add to the Common Name whitelist.

    Note

    You can enter multiple domain names and separate them with commas (,). For example, example.com,example.org,example.net.

  7. Click OK to complete the configuration.