> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/integrating-static-cdn-resource.md).

# Integrating Static CDN Resource

Integrate a Small or Large CDN Resource with your website or application to deliver content through Medianova CDN.

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.

{% hint style="info" %}
Before integrating your CDN resource, ensure that it has been created successfully and is in an active state.

For resource-specific integration guidance, open your CDN Resource and select **Setup Guide** in the Medianova Control Panel.

The Setup Guide displays your CDN URL, provides asset URL examples, and lets you test an existing asset through the CDN.
{% endhint %}

## 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

## Integrate Your CDN Resource

{% stepper %}
{% step %}

### Identify Content to Deliver Through the CDN

Determine which resources should be delivered through the CDN.

For Small CDN Resources, typical static assets include:

* CSS files
* Fonts
* Images
* JavaScript files

Large CDN Resources can be used for larger downloadable or media files according to your resource configuration.
{% endstep %}

{% step %}

### Update Asset URLs

Replace origin URLs with your CDN hostname.

Example:

**Before**

```
<img src="https://example.com/images/logo.png">
```

**After**

```
<img src="https://cdn.example.com/images/logo.png">
```

Apply the same change wherever the selected assets are referenced by your website or application.

{% hint style="info" %}
You can find your resource-specific CDN URL and copyable Image, CSS, and JavaScript examples under **Setup Guide** in the [Medianova Control Panel](https://cloud.medianova.com).
{% endhint %}
{% endstep %}

{% step %}

### Update Your Application or CMS

If your website uses a CMS or web framework, configure it to use the CDN hostname for the selected content.

Depending on your application, this may require updating:

* Asset URL settings
* CDN integration settings or plugins
* Environment variables
* Static asset host configuration
  {% endstep %}

{% step %}

### Allow CDN Access to Your Origin

If your origin server is protected by a firewall, allow requests from Medianova edge servers.

See [**Medianova IP Blocks**](/products/performance-cdn/static-content-delivery/configuration-basics/medianova-ip-blocks.md).

{% hint style="info" %}
See [Medianova IP Blocks](/products/performance-cdn/static-content-delivery/configuration-basics/medianova-ip-blocks.md) for the required network information.
{% endhint %}
{% endstep %}

{% step %}

### Verify Content Delivery

Test an existing asset using its CDN URL and confirm that it loads as expected.

You can also use **Setup Guide → Check your setup** in the Medianova Control Panel. Enter the path of an existing asset and select **Open asset** to test it through the CDN.

When testing through your website or application, use browser developer tools to inspect:

* Cache-related response headers
* HTTP status code
* Request URL
* Response headers
  {% endstep %}

{% step %}

### Validate Cache Behavior

For content intended to be cached, verify that:

* The response is eligible for caching according to the configured cache policy.
* Cache-related response headers have the expected values.
* Subsequent requests exhibit the expected CDN cache behavior.
  {% endstep %}

{% step %}

### Test Your Website or Application

Verify the affected content and application functionality after integration.

Confirm that:

* CDN URLs resolve correctly.
* Images and other assets load successfully.
* CSS and fonts are loaded correctly.
* JavaScript functions as expected.
* Downloadable content remains accessible.
  {% endstep %}
  {% endstepper %}

## Troubleshooting

If content is not delivered as expected, verify that:

* Asset URLs use the correct CDN hostname.
* The requested asset path exists on the origin.
* The origin server is reachable from the CDN.
* Firewall rules allow the required Medianova IP blocks.
* DNS configuration is correct when using a custom domain.
* The configured cache policy matches the expected caching behavior.

For additional troubleshooting guidance, see [Troubleshooting Common Setup Issues](/support-and-troubleshooting/common-issues-and-solutions/troubleshooting-common-setup-issues.md)

### Related Concepts

* [Create Small CDN Resource](/products/performance-cdn/static-content-delivery/create-small-cdn-resource.md)
* [Create Large CDN Resource](/products/performance-cdn/static-content-delivery/create-large-cdn-resource.md)
* [Caching Fundamentals](/api-documentation/performance-cdn/caching.md)
* [Medianova IP Blocks](/products/performance-cdn/static-content-delivery/configuration-basics/medianova-ip-blocks.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/integrating-static-cdn-resource.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.