Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud CDN
    • Overview
    • Points of presence
    • Resource
    • Origins and origin groups
      • Overview
      • TLS certificates
      • CORS
      • Content compression
    • Request redirection
    • Content caching
    • Secure tokens
    • IP-based access policy
    • Country-based access policy
    • Dedicated IP addressing
    • Location rules
    • Log export
    • Labels
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Request logs
  • Audit Trails events
  • Release notes
  • FAQ
  1. Concepts
  2. Data exchange between clients and the CDN
  3. CORS

CORS in Cloud CDN

Written by
Yandex Cloud
Updated at September 14, 2026
View in Markdown

Yandex Cloud CDN supports cross-domain requests via CORS (cross-origin resource sharing).

The CORS setting of a CDN resource controls whether the CDN server adds the Access-Control-Allow-Origin header to its client responses and defines the specific header value. If adding the header is enabled, the CDN server will generate it regardless of whether content is served from cache or fetched from the origin. This setting only applies to the CDN server’s response to the client and does not modify the origin configuration.

In the resource settings, you can:

  • Allow CORS requests with any origins (the Origin header values): Set the Access-Control-Allow-Origin header to * or to the Origin header’s value in the request.
  • Allow CORS requests for specific origins: Set the Access-Control-Allow-Origin header to the value of the Origin header in the request, but only if it is listed as allowed in the settings.
  • Deny CORS requests: Disable adding the Access-Control-Allow-Origin header to responses.

CORS settings apply to all files of the resource.

Note

The CORS setting for a CDN resource only manages the Access-Control-Allow-Origin header in CDN server responses. It does not add other CORS headers and does not generate a response to the preflight OPTIONS request on behalf of the origin.

If the browser sends a preflight request, allow the OPTIONS method in the CDN resource settings and configure the origin to correctly process this request and return the required CORS headers, e.g., Access-Control-Allow-Methods and Access-Control-Allow-Headers. For an Object Storage bucket, configure CORS in the bucket settings.

Useful linksUseful links

  • CORS configuration guide.

Was the article helpful?

Previous
TLS certificates
Next
Content compression
© 2026 Direct Cursus Technology L.L.C.