Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Service page
Yandex Cloud CDN
Documentation
Yandex Cloud CDN
  • Getting started
    • Overview
    • Providers
    • Resource
    • Origins and origin groups
      • Overview
      • Host header
      • Content segmentation
      • Origin shielding
    • Redirecting requests
    • Content caching
    • Secure tokens
    • IP-based access policy
    • Log export
    • Labels
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics for the EdgeCDN provider
  • Monitoring metrics for the Yandex Cloud CDN provider
  • Audit Trails events
  • Release notes
  • Troubleshooting
  1. Concepts
  2. Data exchange between the CDN and origins
  3. Overview

Configuring data exchange between CDN servers and origins

Written by
Yandex Cloud
Updated at August 26, 2025

Note

CDN servers do not support IPv6 and can only access sources at IPv4 addresses.

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 CDN resource with the EdgeCDN provider, you can configure advanced settings. 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.

Was the article helpful?

Previous
Content compression
Next
Host header
© 2025 Direct Cursus Technology L.L.C.