Comprehensive CDN documentation and API references, with integration, troubleshooting and developer guides across all Medianova services.

Learn how to integrate and optimize your workflows with our detailed API documentation.

Medianova provides a range of content delivery, performance optimization, and security services designed to accelerate websites, applications, APIs, and media delivery.

This section introduces the core concepts used throughout the documentation and provides an overview of the main technologies available on the Medianova platform.

A Content Delivery Network (CDN) is a globally distributed network of edge servers that delivers content from locations closer to users. By serving content from the nearest Point of Presence (PoP), a CDN reduces latency, improves response times, and decreases the load on the origin server.

Static Content Delivery is designed to accelerate the delivery of cacheable assets such as images, CSS files, JavaScript, fonts, downloadable files, and other static resources.

Medianova provides Small CDN and Large CDN resource types for static content delivery, allowing organizations to optimize different types of workloads while reducing origin traffic and improving page load times.

Related concepts

WAF is Medianova’s intelligent web security layer that protects your applications from malicious traffic, bots, and exploits. With real-time filtering, custom rule control, and built-in analytics, it helps you prevent attacks before they reach your origin servers.

Medianova WAF combines ease of use, robust protection, and edge-level performance to keep your web applications secure. Unlike standard firewalls, WAF protects against both network and application-layer attacks.

• Edge-level protection – All traffic is filtered at Medianova’s global CDN edge before it reaches your origin.

User Agent ACL allows you to control access to content by evaluating the User-Agent header of incoming requests.

You can create whitelist or blacklist rules using full or partial User-Agent values to allow or deny access for specific browsers, applications, crawlers, or automated clients.

Turn Status to On.

Choose one of the following modes:

• Whitelist — Only matching User-Agent values are allowed.

Fine-tune how your Static CDN Resource connects to the origin and delivers content. Select a configuration area to continue.

Origin Response Timeout defines the maximum time the CDN waits for an HTTP(S) response from your origin server. If the origin does not respond within the configured duration, the CDN returns a 504 Gateway Timeout.

Adjusting this timeout helps maintain predictable performance and prevents long wait times caused by slow origin responses.

You can manage Origin Response Timeout using the or .

In the Medianova Control Panel, go to CDN Resources, select your resource, and navigate to Origin Settings.

Follow the steps below to set the timeout duration.

Rewrite Origin URLs enables you to transform incoming paths before they are forwarded to origin servers. You can configure Match Mode, Origin URI, Target URI, and Priority to adjust how paths are rewritten for directory changes, API restructuring, or backend routing needs.

You can manage Rewrite Origin URLs using the Medianova Control Panel or API.

In the Medianova Control Panel, go to CDN Resources, select your resource, and navigate to Origin Settings

Manage Rewrite Origin URLs

Follow the steps below to add and manage Rewrite Origin URLs for your CDN Resource.

• All files: Applies to every incoming request.

• Path: Matches only the path portion of the request URI.

• Full Path: Matches the exact full URL path.

Issue: Rewrite Origin URL does not apply. Cause: Incorrect Match Mode or Origin URI format. Fix: Verify that the incoming request path matches the defined parameters.

Issue: A different Rewrite Origin URL is applied first. Cause: Priority ordering conflict. Fix: Assign a lower priority value to the entry you want processed first.

Issue: Origin returns 404 after rewrite. Cause: Target URI does not exist on the origin. Fix: Confirm that the target path is valid and reachable at the origin server.

Enable Gzip From Origin allows the CDN to request text-based files from your origin using the Accept-Encoding: gzip header.

If the origin supports gzip, the CDN stores the compressed version in cache; otherwise, it stores the uncompressed response.

Enable Gzip From Origin instructs the CDN to request text-based files from your origin using:

Accept-Encoding: gzip

When enabled:

• The CDN requests gzip-compressed content from the origin. • If the origin supports gzip, the CDN stores the compressed version in cache. • If the origin does not support gzip, the CDN stores the uncompressed response.

This improves performance and reduces bandwidth usage between the Origin → CDN path.

How It Works

The CDN sends Accept-Encoding: gzip to the origin. If the origin supports gzip, compressed content is returned and stored in the cache. If the origin does not support gzip, the CDN caches the uncompressed response.

You can enable this feature via the

Medianova CDN starts sending the Accept-Encoding: gzip header to your origin for eligible file types.

Does this feature compress content for end-users? No. It only optimizes the origin → CDN transfer. Client-side compression is handled separately by .

What if my origin does not support gzip? The CDN will fetch and cache the uncompressed version of the file.

Does this apply to all file types? No. The feature applies only to text-based MIME types. Images are not affected and require Image Optimization.

Cross-origin resource sharing (CORS) is a browser security mechanism that determines whether a web page can load resources from a different origin. While browsers allow cross-origin images, CSS files, scripts, iframes, and videos without restrictions, other request types — such as Ajax calls and web fonts — are blocked by default under the same-origin policy.

CORS defines how browsers and servers evaluate cross-origin requests. Medianova CDN can send the access-control-allow-origin header in HTML responses to enable controlled cross-origin access.

By default, Medianova CDN forwards any CORS-related headers sent by your origin. You only need to enable CORS Header if you want CDN edges to set or override this header.

You can configure CORS Header in the Medianova Control Panel or via the API.

Enable CORS Header

After enabling the feature, Medianova CDN edge servers add the access-control-allow-origin header to HTML responses based on your configuration.

If no domains are defined in the allow list, CDN edges return the following header:

The wildcard * allows any origin to load cross-origin resources from the CDN.

Add domains to restrict cross-origin access to only approved origins.

For example, if https://www.shop.com loads web fonts from https://fonts.shop.com and you want to prevent external sites from using these fonts, add fonts.shop.com to the allow list.

When a domain is added, CDN edges respond with:

• CORS Header applies only to HTML responses.

• If your origin also sets access-control-allow-origin, CDN behavior depends on your Header Override configuration.

• Browser console messages provide the most accurate diagnostics for CORS failures.

Static Content Delivery enables organizations to deliver cacheable content efficiently through Medianova’s globally distributed CDN network. By caching static assets at edge locations, content is served from the nearest available Point of Presence (PoP), reducing latency, minimizing origin traffic, and improving application performance.

This category includes multiple CDN resource types designed for different content delivery requirements, including Small CDN, Large CDN, and Video on Demand (VOD).

Medianova's Static Content Delivery services provide a scalable and secure platform for delivering cacheable content.

• Lower Latency – Serve content from the nearest edge location.

After in the , update your application to deliver content through the CDN instead of your origin server. This page introduces the basic concepts required to configure content delivery and verify that requests are routed through the Medianova CDN.

A newly created CDN Resource progresses through several operational states before it begins serving traffic.

Redirect Handle From Origin allows the CDN to modify request or response headers when the origin returns a 3xx redirect.

You can select which redirect codes to handle and optionally add or modify headers sent during redirection.

This provides greater control over origin-driven redirects and ensures consistent client behavior.

You can manage Redirect Handle From Origin using the or the .

In the Medianova Control Panel, go to CDN Resources, select your resource, and navigate to Origin Settings

Follow the steps below to enable and configure redirect handling for your CDN Resource.

The X-CDN Header feature adds an X-CDN header to requests that are forwarded from the CDN to your origin. This allows your origin to identify that the request is coming through Medianova CDN, which can be useful for logging, routing decisions, and origin-side analytics.

You can configure X-CDN Header in the or via

When the X-CDN Header toggle is enabled:

• The CDN adds the X-CDN header to the origin request during the fetch operation.

Page Rules trigger one or more actions on an incoming request to Medianova CDN whenever a defined URL pattern is matched.

Page Rules are available in the for any CDN resource in the Page Rules tab.

Available include Cache Type, Custom Header, Geoblocking and more.

Page Rules can be configured foror CDN resources of type Small, Dynamic, Large & VOD.

The default number of allowed page rules depends on the package as shown below.

Secure Sockets Layer (SSL) and Transport Layer Security (TLS) are cryptographic protocols that protect data exchanged between clients and servers. Although the term SSL is still widely used, modern HTTPS connections rely on TLS.

Medianova CDN uses SSL/TLS certificates to secure HTTPS connections between end users and CDN edge servers.

Depending on your deployment, you can use a shared certificate, upload your own certificate, or request a free certificate through the SSL / TLS page in the Medianova Control Panel.

Why SSL/TLS Matters

SSL/TLS provides several essential security benefits for websites and applications.

• Confidentiality – Encrypts data exchanged between clients and servers.

• Integrity – Protects data from modification while in transit.

• Authentication – Verifies the identity of the website through trusted Certificate Authorities (CAs).

• Trust – Enables HTTPS, improving user confidence and browser security indicators.

• Performance – Modern TLS versions provide faster and more efficient encrypted connections.

Medianova supports the most common SSL/TLS certificate types.

When a client requests content over HTTPS:

1. The client connects securely to the nearest Medianova edge server.

2. The edge server presents a valid SSL/TLS certificate.

3. A TLS handshake establishes an encrypted connection.

4. The CDN serves cached content or retrieves the requested object from the origin.

This process ensures that data remains protected while traveling across the network.

For secure and reliable HTTPS delivery:

• Enable HTTPS for every production CDN Resource.

• Prefer TLS 1.3 whenever client compatibility allows.

• Keep SSL certificates valid and renewed before expiration.

• Use Wildcard or SAN certificates when serving multiple domains.

The following guides explain how to configure SSL/TLS in the Medianova Control Panel

A PKCS#12 (.pfx) file contains a certificate, private key, and optional intermediate certificates in a single encrypted bundle. Although the SSL / TLS wizard supports uploading .pfx files directly, some environments or workflows require separate .crt and .key files.

This guide explains how to extract the certificate and private key from a PKCS#12 file using OpenSSL.

Prerequisites

Before you begin, ensure that you have:

• A valid PKCS#12 (.pfx) certificate file.

• The password protecting the .pfx file.

• OpenSSL installed on your system.

• (Optional) A descriptive filename such as example_com.pfx.

After extracting the files, you can use either of the following options in the SSL / TLS wizard:

• Upload Certificate Files to upload the generated .crt and .key files.

• Paste Certificate and Private Key to paste their contents directly into the wizard.

If you do not need separate certificate files, upload the original .pfx file directly using the Upload PKCS#12 (.pfx) option.

After creating a Small CDN Resource or Large CDN Resource, you must configure your website or application to deliver static assets through the CDN instead of directly from your origin server.

This guide explains how to update asset references, verify content delivery, and configure your origin environment for successful CDN integration.

Prerequisites

Before you begin, ensure that you have:

• A configured Small CDN Resource or Large CDN Resource

• Access to your website, application, or CMS configuration

• Permission to modify your origin server configuration

• Permission to update firewall rules if required

If assets are not served through the CDN, verify the following:

• Asset URLs reference the CDN hostname.

• DNS configuration is correct.

• Firewall rules allow CDN edge servers.

• Cache policies permit the content to be cached.

Gzip and Brotli compression reduces file sizes by up to 80% for common content types like HTML, CSS and JavaScript, leading to faster load times and improved user experience. This not only enhances website performance and improves SEO / Core Web Vitals, but also decreases bandwidth usage, saving CDN costs and ensuring efficient content delivery.

Compression at the Edge

Gzip compression happens at Medianova Midcache servers, which is then passed on to the Edge servers. Both the Midcache and Edge servers may cache the Gzip compressed content for faster delivery of next responses. Edge servers perform Brotli compression on-the-fly when requested by the client.

Medianova delivers content with Gzip compression, Brotli compression or no compression depending on:

• Values of the Accept-Encoding header in the request coming into Medianova

• Your Medianova configuration (learn how to configure Gzip and Brotli)

You can customize which content types Medianova serves compressed for Gzip and Brotli, except for content of type text/html : this is always compressed.By default, Medianova compresses the following content types:

For responses coming from customer origin server or CDN cache, Medianova performs compression for any status code.Some MN features like Geoblocking may cause MN CDN to serve lightweight, edge-generated error responses and these are always served uncompressed.

If compression is enabled for the requested content type, Medianova applies compression to responses with a minimum size of 400 bytes.

Medianova sends compressed responses without the Content-Length header to prevent browsers receiving possibly incorrect length information as a result of dynamic transformation.

Sending Cache-Control: no-transform on the response from origin has no effect on compression.

Medianova always requests uncompressed content from the customer origin server. The CDN sends no Accept-Encoding header to the origin and expects to receive the response uncompressed and without a Content-Encoding header.

MN uses compression level 6 for Gzip and 5 for Brotli. These compression levels provide an optimal balance between compression efficiency and server CPU consumption.

Yes. When a request is first made, Medianova servers cache the content Gzip compressed. If Gzip is later disabled, the already cached Gzip version will still be served unless a purge is performed or the cached object expires.

Currently, Medianova has no plans for supporting Zstandard-encoded content.

Origin SNI Request enables the CDN to send the correct Server Name Indication (SNI) value when establishing SSL/TLS connections with your origin. This ensures that the origin server selects the appropriate SSL certificate, especially when hosting multiple domains on the same IP address.

Enabling this feature improves compatibility and prevents certificate mismatch errors during HTTPS communication.

You can manage Origin SNI Request using the Medianova Control Panel or API.

In the Medianova Control Panel, go to CDN Resources, select your resource, and navigate to Origin Settings.

Configure Origin SNI Request

Follow the steps below to enable and configure Origin SNI Request for your CDN Resource.

During an SSL/TLS handshake, the CDN includes the SNI extension, which specifies the domain name requested by the client. This allows the origin server to:

• Select the correct SSL certificate

• Support multiple domains on a shared IP

• Avoid certificate mismatch errors

Use this setting when:

• Your origin serves multiple HTTPS domains from the same IP

• The origin requires SNI to present the correct SSL certificate

• You encounter HTTPS 421 or certificate mismatch errors

If SNI is not sent:

• The origin may return the wrong SSL certificate

• HTTPS validation may fail

• Dynamic requests may intermittently fail under multi-domain hosting setups

Issue: HTTPS requests fail with certificate mismatch. Cause: The origin returned the default certificate instead of the certificate for the requested domain. Fix: Enable Origin SNI Request and enter the correct domain.

Issue: Origin returns 421 Misdirected Request. Cause: The origin requires SNI to route the request to the correct virtual host. Fix: Ensure the SNI domain matches the vhost configuration on the origin.

Issue: Requests fail after enabling SNI. Cause: Incorrect domain entered in the Origin SNI Request Domain field. Fix: Confirm that the domain matches a valid certificate installed on the origin.

Advanced Origin Settings allow you to configure granular origin-routing behavior for specific URIs, file types, or directories. By defining rule-based conditions, you can route selected traffic to different origins, override ports, set custom host headers, or assign priorities for complex routing environments.

You can manage Advanced Origin Settings in the Medianova Control Panel or via API.

Log in to the Medianova Control Panel, select a CDN resource in the CDN section, and navigate to the Origin Settings tab.

Advanced Origin Settings use rule-based logic. Each rule defines what request pattern to match and how the CDN should route that traffic.

Add an Origin Rule

This workflow creates a new rule for routing selected requests to a specific origin configuration.

Advanced Origin Settings follow a priority-based evaluation model:

• Highest priority wins. Lower numeric values represent higher priority.

• If multiple rules match the incoming request, the CDN applies the rule with the highest priority.

• If no rules match, the CDN uses the default origin configuration.

Routing decisions consider:

• URI match pattern

• Origin protocol selection

• Domain/IP

• Ports

This allows precise routing for APIs, media directories, file extensions, or multi-origin deployments.

What happens if multiple rules match the same request?

The rule with the highest priority (lowest priority number) is applied.

Do regex or prefix rules impact performance?

Regex rules are more expensive than prefix or extension matches. Use them only when necessary.

What if no Advanced Origin rule matches the request?

The request is sent to the default origin defined in the main Origin Settings section.

For Streaming Content Caching resources, Advanced Origin Settings use a different structure based on Origin Groups and URI Match Rules.

Instead of defining individual origin rules directly, you first create origin groups containing one or more origins, then create URI match rules that route traffic to those groups.

The page has two sections:

• Origin Groups – Define groups of origins for load balancing and failover.

• URI Match Rules – Assign URI patterns to origin groups to route traffic.

You can create up to 50 origin groups, and each group can contain up to 25 origins.

After creating origin groups, define URI match rules to route traffic to the appropriate group.

Prefetch refers to the process of proactively fetching and caching specific files from your origin before any user request occurs. It warms up CDN caches so that the first users receive content instantly, avoiding slow cache misses and offloading your origin server. When you initiate a Prefetch, the CDN pulls the file from your origin and caches it across all CDN POPs. This is especially effective for the delivery of large static or media files.

You can initiate Prefetch operations from the Medianova Control Panel or via the API.

When to Use Prefetch

Use Prefetch to:

• Preload content before a scheduled event, campaign, or content release

• Ensure large static files (e.g., videos, software downloads) load instantly

• Avoid cache-miss latency for the first user(s)

• Offload your origin by serving assets from CDN edge locations

1. You submit one or more file paths via the Medianova Control Panel or .

2. Medianova CDN initiates an HTTP GET request to your origin for each file.

3. If the file is not already cached, it is fetched and stored across CDN edge locations.

When you initiate a Prefetch, the CDN issues an HTTP GET request to your origin and stores the file in cache across all CDN POPs (Points of Presence). This ensures that the file is readily available globally, without waiting for actual user traffic to trigger cache population.

Unlike Purge, which invalidates cached content, Prefetch only populates caches if the file is not already cached. If the file already exists in cache, Prefetch will not re-fetch it from origin.

Prefetch Type

Medianova supports single-file Prefetch, which allows fetching and caching a specific file from your origin.

• Prefetch only frequently accessed static files, such as videos, images, or large downloads.

• Use Purge + Prefetch together to refresh caches after file updates.

• Schedule Prefetch operations during off-peak hours to minimize origin load.

Custom Error Page allows you to redirect users to a custom URL when specific HTTP error codes are generated by the CDN edge.

This feature is commonly used to display branded error pages, access restriction notices, or custom user guidance instead of the default CDN error response.

How It Works

When the CDN generates a configured HTTP error response, it returns a redirect to the specified Error Page URL instead of displaying the default error page.

Each rule consists of three parameters:

Multiple rules can be configured for different HTTP status codes.

In the , navigate to the CDN Resource and open the Page Rules tab.

Defines the edge-generated HTTP status code that triggers the redirect.

Supported values range from 400 to 599.

Defines the URL users are redirected to when the configured status code occurs.

The URL should be publicly accessible and return a valid response.

Defines the redirect response returned to the client.

Common values include:

For additional details about redirect responses, see the HTTP Response Codes documentation.

The following configuration:

• Status Code: 403

• Error Page URL: https://www.example.com/access-denied.html

• Redirect Status Code: 302

redirects users to a custom access-denied page whenever the CDN generates a 403 response.

Display a custom message when access is restricted based on visitor location.

Provide additional information when requests are denied by access control policies.

Present branded error pages instead of generic CDN error responses generated by edge-level security features.

• This feature applies only to edge-generated error responses.

• Origin-generated error pages are not affected.

• The Error Page URL must remain accessible to users.

• Redirect loops should be avoided when hosting custom error pages on protected resources.

Purge invalidates cached content across the Medianova CDN before its cache lifetime (TTL) expires. It ensures that updated content from your origin is immediately reflected and consistently served from all cache layers worldwide.

When a purge is executed, the Medianova purge system distributes invalidation commands across the CDN’s cache hierarchy. Cached objects are marked as expired and fetched again from your origin upon the next user request.

You can trigger a purge from the Medianova Control Panel or via API .

When to Purge Cached Content

Use purge whenever:

• Updated HTML, CSS, JS, images, or video files must be reflected immediately.

• Outdated or sensitive content needs to be removed from CDN caches.

• New deployments or configuration changes require instant cache refresh.

• Consistency across all cache layers is required after a content update.

Medianova supports multiple purge methods to give you flexibility and control:

1. A purge request is initiated via the Medianova Control Panel or .

2. Medianova’s purge system distributes invalidation commands to all cache layers.

3. Cached objects matching the path are marked as invalid and no longer served.

Purge requests propagate through all layers of Medianova’s caching infrastructure extremely quickly – typically completing across our global network in under 5 seconds – ensuring that outdated content is swiftly replaced with fresh content worldwide.

• Purge only what’s needed. Avoid full purges to reduce cache refill load.

• Use specific paths instead of broad wildcard patterns whenever possible.

• Automate with API purge to clear cache after deployments or content updates.

SSL/TLS certificates enable encrypted HTTPS communication between users and CDN Resources. From the SSL / TLS page, you can upload your own certificates or request free Let's Encrypt certificates using a guided provisioning wizard.

Manage your certificates from the SSL / TLS page in the

1. Open SSL / TLS from the left navigation menu.

2. Review the certificates currently available in your account.

Free SSL certificates allow you to secure your CDN Resources using Let's Encrypt without purchasing or managing a commercial SSL certificate.

After requesting a Free SSL certificate, Medianova guides you through the required DNS validation process and automatically issues the certificate once domain ownership has been verified.

Request Free SSL certificates from the SSL / TLS page in the .

For the certificate creation workflow, see .

Free SSL certificates require DNS/CNAME validation before they can be issued. The requested domain must resolve to the Medianova edge network.

Create a new certificate from the SSL / TLS page by selecting Free SSL in the certificate wizard.

The CNAME & SSL tab allows you to associate one or more custom domains with a CDN Resource and configure the SSL certificate and supported TLS versions used to secure client connections.

Before configuring SSL, ensure that your custom domain points to the hostname assigned to your CDN Resource and that an appropriate SSL certificate is available in your organization.

Accelerate personalized, database-driven, or API-based content with Medianova’s Dynamic CDN. Cache dynamic responses at the edge to reduce origin load and deliver faster user experiences.

Dynamic Content Acceleration improves the delivery of content that is generated by an application rather than served as static files. Unlike images, JavaScript, or CSS, dynamic responses are created in real time and often depend on user sessions, request parameters, application logic, or backend data.

Medianova's Dynamic CDN reduces response times by combining intelligent request routing, edge caching, optimized origin communication, and configurable cache policies. These capabilities improve application performance while maintaining content freshness.

Static content can typically be cached for long periods because it rarely changes. Examples include:

The Origin SNI Request feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It ensures the CDN includes the correct Server Name Indication (SNI) during the TLS handshake when forwarding dynamic HTTPS requests to your origin. This enables the origin server to select the appropriate SSL certificate and prevents certificate mismatch issues in multi-domain environments.

For configuration details, expected behavior, and examples, refer to the main documentation: Learn more in the Origin SNI Request documentation.

The Enable Gzip from Origin feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It instructs the CDN to include Accept-Encoding: gzip when requesting eligible text-based content from your origin. If the origin supports gzip, the CDN stores the compressed response; otherwise, it stores the uncompressed version. This reduces bandwidth usage on the origin → CDN path and improves overall delivery efficiency for dynamic workloads.

For configuration details, supported MIME types, and examples, refer to the main documentation: Learn more in the Enable Gzip from Origin documentation.

A VOD Resource is designed for delivering on-demand video content through Medianova's edge network. Content can be retrieved from your own origin infrastructure or from Stook Object Storage.

When to Use a VOD Resource

Use a VOD Resource for:

• On-demand video libraries

• Prerecorded video content

• Adaptive HLS or DASH delivery

• Video files that require automatic packaging

• Video content stored on your origin server or in

• VOD Resources are intended for prerecorded video content, not live RTMP ingest.

• Medianova VOD Packaging is available when Stook Object Storage is selected as the source.

• Enabling VOD Packaging transcodes compatible source files into adaptive bitrate HLS and DASH renditions.

Create and manage VOD Resources from the .

Navigate to CDN and select Create CDN Resource to launch the Create CDN wizard.

Verify CDN connectivity using:

Replace:

• example.mncdn.com with your VOD Resource hostname.

• /path/to/video.mp4 with a valid video file.

This command:

• Sends an HTTP GET request to the CDN.

• Displays the request and response headers.

• Shows the remote edge IP address.

• Discards the response body.

Use a URL that returns HTTP 200 OK. If a custom CNAME is configured, validate using the custom hostname.

If the resource does not serve content correctly:

• Verify that the origin server is reachable.

• Confirm that the configured origin ports are accessible.

• Ensure that the requested video exists in the configured origin path or Stook Bucket.

• Allow VOD Packaging to complete before requesting generated HLS or DASH outputs.

HTTP/2 improves content delivery performance by allowing multiple requests and responses to be multiplexed over a single connection. This reduces latency, minimizes connection overhead, and improves page load efficiency for supported clients.

You can manage HTTP/2 in the Medianova Control Panel.

Navigate to the relevant CDN Resource and open the Protocol Optimization section.

Configure HTTP/2

Behaviour

• HTTP/2 is used automatically when supported by the client.

• Multiple requests can be transferred over a single connection.

• Clients that do not support HTTP/2 automatically fall back to earlier HTTP versions.

• This setting affects client-to-CDN communication only.

• Reduces connection overhead.

• Improves page load performance.

• Reduces latency for websites with many assets.

• Improves network efficiency through multiplexing.

Do all browsers support HTTP/2? Most modern browsers support HTTP/2. Unsupported clients automatically use an earlier HTTP version

Does enabling HTTP/2 require application changes? No. HTTP/2 is negotiated automatically between the client and the CDN.

Does this setting affect communication with the origin server? No. It only controls the protocol used between clients and the CDN edge.

The X-Content-Type-Options feature adds the X-Content-Type-Options header to viewer responses. This header instructs compatible browsers not to perform MIME sniffing and to rely strictly on the Content-Type declared by the server. Disabling MIME sniffing helps reduce exposure to certain injection and cross-site scripting (XSS) vectors.

How X-Content-Type-Options Works

You can configure X-CDN Header in the Medianova Control Panel or via API

When enabled:

• The CDN adds the following header to viewer-facing responses:

  Copy

  X-Content-Type-Options: nosniff

• Browsers that support this header will not attempt to infer content types and will instead enforce the value provided by the origin.

• MIME sniffing is disabled for resources such as scripts, stylesheets, and other content types that could be misinterpreted.

Ensure the browser does not guess content types, avoiding scenarios where a file may be interpreted as executable code.

Reduce attack surfaces where incorrect content-type interpretation could lead to script execution.

Guarantee consistent behavior across browsers by ensuring content is processed exactly as declared.

• The header is applied only to viewer responses, not to origin-bound requests.

• Modern browsers widely support nosniff, but legacy browsers may behave inconsistently.

• Enabling this header does not alter your CDN caching logic.

A Large CDN Resource is designed for large downloadable objects and live streaming workloads. It supports static large-file delivery from a customer origin or Stook Object Storage, as well as live stream delivery through an existing streaming origin or RTMP Push.

Use a Large CDN Resource for:

• Large downloadable files such as video, audio, .zip, and .exe files

Static CDN is primarily used for delivering fixed content, such as images, CSS files, and JavaScript files. These resources are typically unchanged, which allows for faster delivery through a CDN. The Static CDN Analytics section provides key metrics that help monitor, analyze, and optimize the performance of static content delivery. These metrics focus on the caching effectiveness, the amount of traffic being served from the cache versus the origin server, and the overall bandwidth usage.

• Total Traffic: This chart displays the total amount of traffic delivered during a selected time range. Users can view the traffic over a custom time range or compare it with the previous time range to understand the trends and fluctuations in traffic. A significant increase in traffic indicates that the content is being accessed more frequently, which can be beneficial for scaling infrastructure and improving cache efficiency.

Settings control the actions Medianova CDN takes once a request matches the URL pattern defined in a page rule.

The table below outlines all settings available in Page Rules from the .

ETag Verification ensures that cached objects remain synchronized with the origin after cache expiration.

When enabled, the CDN stores the ETag header returned by the origin and performs conditional validation after the cache TTL expires. If the ETag value has changed, the cached object is refreshed; otherwise, the existing cached version continues to be served. This helps reduce unnecessary data transfer while maintaining content consistency.

You can manage ETag Verification in the or via .

Select a CDN resource in the CDN section, and navigate to the Caching tab.

Enable or disable ETag validation to ensure cached content remains synchronized with the origin.

Medianova’s CDN uses specific IP address ranges to fetch content from your origin servers. If your origin server uses a firewall or IP-based access controls, you must allow all addresses listed below to ensure reliable access from Medianova edge servers. This allows the CDN to retrieve and deliver your content securely and efficiently.

After configuring your Dynamic CDN Resource, verify that requests are served through the Medianova CDN before directing production traffic to the resource.