Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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
  • Getting started
    • Overview
    • Points of presence
    • Resource
    • Origins and origin groups
      • Overview
      • Host header
      • Content segmentation
      • Origin shielding
      • Following request redirects
      • Hiding of origin headers
    • Request redirect
    • Content caching
    • Secure tokens
    • IP-based access policy
    • Location rules
    • Log export
    • Labels
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Request logs
  • Audit Trails events
  • Release notes
  • Troubleshooting
  1. Concepts
  2. Data exchange between the CDN and origins
  3. Following request redirects

Following request redirects

Written by
Yandex Cloud
Updated at February 24, 2026

By default, when a source returns the 3xx redirect code, Cloud CDN caches this response and returns it to the client. Using the redirects feature, you can enable the CDN resource to follow redirects from the source. With this feature on, Cloud CDN send a request to the address specified in the response and then returns the content from the target address to the client.

This feature uses one redirection level only: if after the first redirect the 3xx code is returned again, it will be forwarded to the client and cached on the CDN.

Note

The option works only if the origin shielding function is on.

You may need to follow redirects in the following scenarios:

  • Content migration: when moving files to a different domain or server.
  • Load balancing: when distributing requests between multiple origins.
  • A/B testing: when switching traffic between different content versions.

See alsoSee also

  • Setting up how to follow request redirects
  • Enabling origin shielding

Was the article helpful?

Previous
Origin shielding
Next
Hiding of origin headers
© 2026 Direct Cursus Technology L.L.C.