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. Hiding of origin headers

Hiding of origin headers

Written by
Yandex Cloud
Updated at February 26, 2026

By default, Cloud CDN provides all HTTP headers received from the origin to the client. With the header hiding option, you can configure your CDN resource in a way that the client gets only particular origin headers.

This option works as a whitelist. All origin headers not mentioned in the setting will be screened and hidden.

You may want to hide headers in some of the following situations:

  • Protecting sensitive information.
  • Enforcement of requirements prohibiting the transmission of certain headers to clients.
  • Downsizing the response.

RecommendationsRecommendations

We recommend whitelisting the following headers:

  • Content-Type: Required for the browser to display content correctly.
  • Content-Length: Informs about the size of the response.
  • Cache-Control: Manages client-side caching.
  • ETag: Used to check content for relevance.
  • Last-Modified: Date of last content modification.

We recommend to hide the following headers for increased security:

  • Server: Server software info.
  • X-Powered-By: Technology info, e.g., PHP, ASP.NET.
  • X-AspNet-Version: ASP.NET version.
  • X-Generator: CMS or website generator info.
  • X-Debug-Info: Debugging info.
  • X-Internal-*: Any internal headers.

See alsoSee also

  • Setting up hiding of origin headers

Was the article helpful?

Previous
Following request redirects
Next
Request redirect
© 2026 Direct Cursus Technology L.L.C.