Skip to content
Myra Online Help Updated · 21 Aug 2026

Set up Myra CDN

Note

The cache settings do not allow objects to be cached that have a No-Cache rule in the header, such as Cache-Control: (no-store|no-cache|private) or Cache-Control: max-age=0.

The Myra Content Delivery Network (CDN) is a globally distributed infrastructure designed to deliver web content, digital assets and applications to end users with high availability, security and low latency.

The Myra globally distributed network routes traffic through RAM-based edge nodes rather than forwarding requests to the customer infrastructure. This reduces the load on the customer infrastructure and eliminates infrastructure bottlenecks. Performance remains consistent regardless of geographic user distribution or traffic spikes.

As a Security-as-a-Service solution, Myra CDN requires no additional hardware or software installation on the customer side. The CDN delivers all static and dynamic web content over HTTPS with full IPv4 and IPv6 support, including high-resolution images, video, scripts, stylesheets, and API responses. The service is designed and operated in Germany, in compliance with the requirements of the German Federal Office for Information Security (BSI) and applicable GDPR obligations.

The CDN forwards traffic not served from the cache to the customer infrastructure over a secured reverse proxy connection with configurable protocols, TLS parameters, and failover behaviour.

The service is managed via the Myra dashboard or fully automated through the REST API, enabling integration into CI/CD pipelines, infrastructure-as-code tooling, and partner platforms. Myra CDN can be combined with additional Myra products such as DDoS Protection, WAF, and Bot Management to extend security coverage beyond content delivery.

As a standalone product, Myra CDN provides protection against the following attacks:

  • Attacks through exposure of the customer infrastructure and through bypassing of the customer infrastructure: Anycast hides the IP address of the customer infrastructure. mTLS CDN to Origin ensures the customer infrastructure only accepts connections from the CDN.
  • Unauthorized client access: mTLS Client to CDN rejects any client without a trusted certificate at the edge.
  • Content theft and hotlinking: Signed URLs enforce time-limited, cryptographically signed access to protected resources.
  • Traffic spikes and basic origin overload: Caching absorbs traffic spikes for cacheable content. Anycast spreads load across PoPs. The CDN serves stale content if the customer infrastructure is unreachable.
  • Known-bad-actor traffic: IP Allow/Blocklists block malicious IPs or CIDR ranges at the edge.
  • Protocol-level attacks: HTTPS enforcement, HSTS, TLS version pinning, and HTTP method restrictions prevent downgrade attacks, SSL/TLS stripping, and method abuse.

Before you can cache your website content with Myra, you must perform the following steps:

  • ► Enabling caching
  • ► Add cache rule
  • ► Checking caching

Once caching is set up, the following configurations are available:

  • ■ Edit cache rule
  • ■ Delete cache rule