Integrating Static CDN Resource

Learn how to integrate your Medianova Small or Large CDN Resource with your website to deliver static assets or large media files through the CDN.

After creating a Small or Large CDN Resource in the Medianova Control Panel, you must integrate it with your website or application so that your static and media assets are delivered through the CDN instead of your origin. This guide explains how to update your asset URLs, firewall configuration, and CMS settings to ensure seamless content delivery via Medianova CDN.

Prerequisites

• A Small CDN Resource or Large CDN Resource already created in the Medianova Control Panel

• Access to your website’s HTML, CSS, JS, or CMS configuration.

• Ability to modify firewall rules on your origin server.

For websites with both static and video content, you can use separate CDN Resources (Small + Large) under the same account and domain structure.

1

Identify assets for CDN delivery

List all assets that can benefit from CDN acceleration:

• For Small CDN Resource: images, CSS, JavaScript, fonts, and similar static content.

• For Large CDN Resource: videos, downloadable files, or other large media assets.

2

Update URLs in HTML code

Replace existing URLs with the corresponding CDN URLs.

Before	After
<img src="https://yourdomain.com/images/example.jpg" alt="Example Image">	<img src="https://CDN_URL/images/example.jpg" alt="Example Image">

3

Update CSS file references

Update references inside CSS files (e.g., images, fonts, or icons).

/* Before */
background-image: url('/images/background.jpg');

/* After */
background-image: url('https://CDN_URL/images/background.jpg');

4

Update JavaScript file references

Ensure that all script sources are loaded from the CDN.

Before	After
<script src="/scripts/example.js"></script>	<script src="https://CDN_URL/scripts/example.js"></script>

5

Check relative paths

Confirm that relative paths continue to work correctly after switching to CDN URLs. Adjust directory structures if required.

6

Verify all resources

Open your website and confirm that assets load from CDN URLs.

Use browser DevTools → Network tab to verify requests.

7

Update CMS or framework settings

If you use a CMS (WordPress, Drupal, Joomla, etc.), configure its CDN or performance plugin to automatically replace static URLs with CDN URLs.

8

Allow Medianova IPs in your firewall

Add Medianova’s CDN IP ranges to your origin’s firewall allowlist to permit content fetches from edge servers. See Medianova IP Blocks

If your origin firewall blocks Medianova IPs, CDN requests will fail. Always verify your allowlist configuration.

9

Test in all environments

Test both staging and production environments to ensure the CDN works correctly and does not break content delivery.

10

Monitor and optimize performance

Use MNLogz Analytics to monitor cache hits, latency, and traffic volume. Refine cache rules or resource paths if needed.

11

Review SEO and canonical tags

When assets move to CDN URLs, update sitemaps and robots.txt if required. Ensure that canonical tags still point to your main domain to prevent duplicate content indexing.