If multiple origin server addresses are configured for your domain name, the origin protocol is HTTPS, and the domain names that provide web services are different from each other, you can specify different Server Name Indication (SNI) values to redirect requests to different origin server addresses. This way, the origin servers return different SSL certificates to points of presence (POPs) based on the SNI value. This allows POPs to establish SSL connections with different origin server addresses.
Prerequisites
The permissions to specify an SNI for each origin have been obtained. By default, this is unavailable to external users. To request the permissions, submit a ticket.
Differences between a specified origin SNI and the default origin SNI
You can specify origin SNIs for different origin servers.
You can configure a default origin SNI for all origin servers. For information about the default origin SNI, see Configure SNI.
If both the specified SNI and default SNI are configured, the former takes effect.
Procedure
Log on to the DCDN console.
In the left-side navigation pane, click Domain Names.
On the Domain Names page, find the domain name that you want to manage and click Configure.
In the left-side navigation tree of the domain name, click Origin Fetch.
On the Configurations tab, click Add in the Specify Origin SNI section.
In the Specify Origin SNI dialog box, configure the parameters. The following table describes the parameters.
Parameter
Description
Origin Server Address
The origin server address for which you want to specify an SNI.
SNI HOST
Follow Origin Address:
Description: The SNI value is the origin server address.
Scenario: The origin server address is a domain name, and SNI verification on the origin server requires the domain name of the origin server.
Follow Origin Host:
Description: The SNI value is the origin host.
Scenario: SNI verification on the origin server requires the origin host.
Custom:
Description: You can specify a custom SNI value.
Scenario: SNI verification on the origin server does not require the domain name of the origin server or the origin host.
Persistent Connection SNI
On: POPs redirect requests that have different SNI values to origin servers by using different persistent connections. This avoids SNI conflicts over the same persistent connection.
Off: Only one SNI value can be used over a persistent connection between a POP and an origin server.
Click OK.