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:

• The value of the HTTP Host header for CDN server requests to origins: the primary domain name used for content distribution, echoing the value from the client's request, or an arbitrary value.
• Other HTTP headers in CDN server requests to origins (see instructions).
• Receiving of files by CDN servers from origins in parts: content segmentation.

For a resource in Cloud CDN, you can specify additional settings provided by EdgeCenter, a CDN provider. For a complete description of its features, see the CDN provider's API documentation. To enable additional options, request access to them from technical support.

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 a URI with the http scheme to a URI with the https scheme, you must select the HTTPS protocol for the resource, and vice versa.