Configuring data exchange between CDN servers and origins

You can select a protocol for communication between CDN servers and origins: always HTTP, always HTTPS, or the protocol used by the CDN server to communicate with the client.

To enable CDN servers to establish HTTPS connections with origins, you need to configure the domain names of the origins yourself, including issuing TLS certificates for them. For instance, you can use Yandex Certificate Manager: issue a certificate from Let's Encrypt^® and get its contents.

For a resource, you can also configure:

• HTTP Host header value in CDN server requests to origins: the primary domain name for content delivery, value copied from the client request, or an arbitrary value.

• Other HTTP headers in CDN server requests to origins (see instructions).

• Receiving segmented files from origins by CDN servers: content segmentation.

• Following request redirects received from content origins.

• Custom server name for SNI (Server Name Indication) when establishing an HTTPS connection from CDN servers to the origin.

  This setting is only available when using an HTTPS connection between the CDN servers and the origin. The SNI protocol is used when the origin works on a virtual hosting or is not associated with a separate IP address. If there are multiple SSL certificates installed on the origin, SNI allows you to correctly select the relevant one for each connection. For more information, see Configuring a custom server name for SNI.

Your resource and origins must be configured so that requests from CDN servers are allowed, processed correctly, and not redirected.

For example, if origins redirect requests from http URIs to https URIs, select HTTPS for the resource, and vice versa.