CDN Configuration Basics
Medianova CDN Configuration Basics document is designed to help you understand and implement the fundamental configurations necessary to leverage the full potential of Medianova's Content Delivery Network (CDN). Whether you are a web developer, content creator, or IT professional, this guide will walk you through essential concepts and steps to optimize content delivery, enhance performance, and improve user experience.
Key Concepts
Before we delve into the configuration details, let's familiarize ourselves with some key concepts specific to Medianova CDN:
Medianova CDN: A robust Content Delivery Network designed to accelerate content delivery, improve website performance, and ensure a seamless user experience.
Edge Servers: Strategically positioned servers that cache and deliver content to end-users, reducing latency and improving load times.
Origin Server: The primary server where the original web content is hosted. Medianova CDN retrieves content from the origin server and caches it on edge servers for efficient delivery.
Origin URL: The URL address of your origin server that holds your contents.
CDN URL: The URL address that will be integrated into your website for CDN integration and where users reach the content.
Creating a Medianova CDN Resource
To get started with Medianova CDN, follow these steps:
Log in to www.cloud.medianova.com with your username and password.
Click on the Create CDN Resource tab in the left menu.
Choose any resource type and fill in the necessary fields.
Create a resource and configure the necessary settings.
The resource you created will be in a "pending" status. Below is information about the resource statuses:
About the status of resources
Pending: The URL entered by the user is marked as "Pending" until the DNS resolution is complete. In this state, the domain name provided by the user has not yet been resolved to an IP address. While the DNS resolution process is ongoing, the resources are not yet accessible through the CDN.
Active: Once the DNS resolution for the URL is successfully completed, the resource status changes to "Active." In this state, the domain name has been resolved to an IP address, and the resource is accessible via the CDN. The resource is activated across all data centers and is optimized to provide the best performance to users.
Passive: If the resource becomes unavailable for any reason, the resource status changes to "Passive." In this state, the resource is inactive, and users cannot access it.
Configuration
The CDN URL and the ORIGIN URL below are examples.
Origin URL | |
|---|---|
CDN URL |
You must replace the existing domain on website code with the CDN URL for contents that you want to serve from CDN.
Examples of HTML code illustrating how to configure a CDN URL with the Origin URL:
Origin URL
<img src=”http://yourdomain.com/images/logos/logo.jpg” alt=”” />
or
<img src=”/images/logos/logo.jpg” alt=”” />
CDN URL
<img src=”yourresourcename.mncdn.com/images/logos/logo.jpg” alt=”” />
Source codes are replaced with the CDN URL instead of the Origin URL as mentioned above.
Thus, our CDN service becomes active on your site.
In order to access your content, you also need to define our IPs in your firewalls. Click to access the IP list of Medianova.
When a resource update is initiated, it goes through one of the following three statuses to indicate the progress and outcome of the configuration deployment to CDN servers. These statuses provide insight into whether the deployment is complete, ongoing, or unsuccessful.
Up to Date:
When the configuration status is marked as "Up to Date", it indicates that all configurations have been successfully deployed and distributed to the CDN servers. The resource is fully operational and ready for use.
Pending:
If the configuration status is "Pending", it means the configurations are still being processed and sent to the CDN servers. During this time, the updates are not yet fully applied. Please wait for the process to complete.
Failed:
When the configuration status is "Failed", it signifies that the deployment to the CDN servers was unsuccessful. In this state, the configurations have not been applied, and troubleshooting or re-deployment is required to resolve the issue.