> 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

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.
{% 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 Cacheable Assets

Determine which resources should be delivered through the CDN.

Typical static assets include:

* Images
* CSS
* JavaScript
* Fonts
* Documents
* Downloadable files
* Video files (Large CDN Resource)
  {% 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 principle to CSS, JavaScript, fonts, and other static assets.
{% endstep %}

{% step %}

### Update Your Application or CMS

If your website uses a CMS or web framework, configure it to serve static assets from the CDN.

Depending on your platform, this may involve:

* Updating the application's asset URL
* Configuring a CDN plugin
* Changing the static asset host
* Updating environment variables
  {% 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" %}
Blocking CDN edge servers prevents cache misses from reaching your origin.
{% endhint %}
{% endstep %}

{% step %}

### Verify Content Delivery

Open your website and confirm that assets are delivered through the CDN hostname.

Browser Developer Tools can be used to verify:

* Request URL
* Response headers
* HTTP status codes
* Cache headers
  {% endstep %}

{% step %}

### Validate Cache Behavior

Confirm that:

* Static assets are cacheable.
* Responses include the expected cache headers.
* Requests are served from the CDN after the initial origin fetch.
  {% endstep %}

{% step %}

### Test Your Website

Verify that:

* Images load correctly.
* CSS is applied.
* JavaScript functions normally.
* Fonts are accessible.
* Downloadable files remain available.

Perform testing in both staging and production environments whenever possible.
{% endstep %}
{% endstepper %}

## Troubleshooting

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.
* The origin server responds successfully.

### 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)
* [Troubleshooting Common Setup Issues](/support-and-troubleshooting/common-issues-and-solutions/troubleshooting-common-setup-issues.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.