> 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/configuration-basics.md).

# Configuration Basics

Learn the basic concepts for integrating a CDN Resource with your website or application.

After [creating a CDN Resource](/products/performance-cdn/static-content-delivery/create-small-cdn-resource.md) in the [Medianova Control Panel](https://cloud.medinova.com), 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.

### Understand the resource lifecycle

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

<table><thead><tr><th width="143.3333740234375">Status</th><th>Description</th></tr></thead><tbody><tr><td><strong>Pending</strong></td><td>The resource is being provisioned and is not yet ready to serve traffic.</td></tr><tr><td><strong>Active</strong></td><td>The resource is fully deployed and available to serve requests through the CDN.</td></tr><tr><td><strong>Passive</strong></td><td>The resource is disabled or unavailable and cannot serve traffic.</td></tr></tbody></table>

{% hint style="info" %}
Resource provisioning time depends on the selected product and configuration.
{% endhint %}

### Identify your origin and CDN hostnames

A CDN Resource is identified by two different hostnames.

<table><thead><tr><th width="151.6666259765625">Hostname</th><th width="231.3333740234375">Example</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Origin URL</strong></td><td><code>https://www.example.com</code></td><td>The source server that stores your content.</td></tr><tr><td><strong>CDN Hostname</strong></td><td><code>yourresource.mncdn.com</code></td><td>The hostname that delivers content through the Medianova CDN.</td></tr></tbody></table>

### Update your application

Replace references to your origin hostname with the CDN hostname for assets that should be delivered through the CDN.

#### Before

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

or

```
<img src="/images/logo.png" alt="Logo">
```

#### After

```
<img src="https://yourresource.mncdn.com/images/logo.png" alt="Logo">
```

After updating these references, requests for the selected assets are served through the CDN instead of directly from the origin.

### Allow CDN access to your origin

If your origin server is protected by a firewall or IP allowlist, permit requests from the Medianova CDN.

Use the published list of Medianova edge IP addresses when configuring your firewall.

**Related documentation**

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

### Related guides

Continue with the guide that matches your CDN Resource type:

* [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)
* [Create VOD Resource](/products/performance-cdn/static-content-delivery/create-vod-resource.md)
* [Create Dynamic CDN Resource](/products/performance-cdn/dynamic-content-acceleration/create-dynamic-resource.md)
* [Integrate a Dynamic CDN Resource](/products/performance-cdn/dynamic-content-acceleration/integrating-dynamic-cdn-resource.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/configuration-basics.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.