Introduction

Medianova is a global provider of Content Delivery Network (CDN) and cloud security services designed to accelerate and secure digital experiences. With over 50 data centers across 21 countries, it helps businesses deliver fast, reliable websites, applications, and APIs while ensuring high performance and robust security.

Key Services and Concepts

1. CDN (Content Delivery Network) A CDN optimizes content delivery by distributing it across multiple servers around the world. Medianova's CDN service ensures that content such as images, stylesheets, and scripts are delivered efficiently by caching static assets at strategically located servers. This minimizes latency and improves page load times for users.

2. Static CDN The Static CDN service is specifically designed to optimize the delivery of static content. By caching assets globally, it ensures that users receive content from the nearest server, drastically reducing load times and enhancing performance. Integration is simple, with users needing only to update asset URLs and configure settings via the Medianova platform.

3. Dynamic Content Caching Dynamic content, generated per user request, can be resource-intensive. Medianova's microcaching system allows for caching dynamic content (e.g., API responses or web pages) for brief periods, thus reducing server load and improving page speeds. This helps reduce bandwidth costs while enhancing the user experience.

4. Live Streaming Medianova provides high-quality live streaming with adaptive streaming technology. This ensures optimal video quality across devices, from desktop to mobile, while maintaining seamless playback. The platform integrates with major social media platforms for broader reach. Security features, including encryption and access controls, ensure that content is protected and accessible only to authorized users.

5. Private CDN For organizations requiring greater control, the Private CDN offers flexible, secure, and high-performance content delivery. It provides businesses with tailored solutions that allow enhanced security and content distribution management.

6. Image Optimization Medianova offers real-time image optimization. This feature allows on-the-fly image transformations such as resizing, cropping, and watermarking through simple URL calls. It also supports responsive images, ensuring that content is tailored for different devices and screen sizes, contributing to faster load times and better user experiences.

7. Stook - Cloud Object Storage Stook is Medianova's cloud object storage solution that enables businesses to store, manage, and retrieve data quickly and reliably. It is S3-compatible and eliminates the traditional barriers of egress and transaction fees, making it a cost-effective choice for scalable storage needs.

8. SSL Encryption Secure Socket Layer (SSL) ensures encrypted communication between a server and a client. Websites with SSL certificates are considered secure, and this encryption is critical for e-commerce platforms, where security is a primary concern for users.

9. Medianova WAF (Web Application Firewall) Medianova's WAF actively monitors all incoming web traffic to detect and block malicious patterns before they can affect web assets. With predefined Managed Rules, enabling these rules offers immediate protection against various security threats.

10. DDoS Protection Medianova's DDoS protection system is always active, offering continuous defense against common attack types, such as DNS Query Floods, SlowLoris, and HTTP floods. It includes several mitigation strategies, including rate limiting, IP blocking, and geoblocking, ensuring minimal disruption to services during attacks.

Conclusion

Medianova combines advanced caching, acceleration, and security features to help businesses create fast, reliable, and secure digital solutions. With global infrastructure, robust security, and easy integration, Medianova empowers businesses to deliver superior user experiences while ensuring high performance and protection against a wide range of threats.

Secure Socket Layer(SSL) provides secure, encrypted communications between a server and client. A website with an SSL certificate is considered safe. Generally, The most important reason for e-commerce sites to be preferred by users is whether they are secure.

The Http protocol has been used for many years to provide communication in the Internet world. But http is not very secure and has turned into HTTPS over time. Https is a protocol used to secure data exchange on the network. This protocol in order to provide security performs an encrypted connection with SSL / TLS.

We have explained the types of certificates you can choose for you first, and then the steps that should be followed to define SSL certificate via Medianova CDN in the cases where the SSL certificate received is .pfx.

Certificate Types

There are many different types of SSL certificates. Below you can find explanations about the most common types of certificates.

1. Wildcard SSL Certificate

Wildcard SSL Certificate is a type of certificate that can be used for all of the subdomains of a certain domain. Wildcard SSL also supports Sub-names of the domain. For example; http://www.yourdomain.net , http://yourdomain.net , http://admin.yourdomain.com , *.yourdomain.net.This type of certificate is supported by all browsers such as Internet Explorer, Mozilla, Chrome. The wildcard is the type of certificate which is ideal for e-commerce and sites requiring a secure login.

2. SAN supported SSL

Certificates are generally purchased for a hostname (main domain). However, there is another type of certificate that supports more than a domain name, and its called SAN. SAN-hosted certificates may vary in hostname permissions. It will be wise to obtain a SAN-supported SSL certificate after you have decided about the number of domains to be served and the type of service you will be serving.

3. Code Signing SSL Certificate

The code signing certificate usually is used by software developers and they digitally sign aps and other software to verify the end-users that the code they are receiving hasn’t been altered or compromised by a third party.If you want to request an SSL certificate for your own server or a code/driver, you need to create a certificate signing request (CSR). This defines both the server that will use your certificate and the domain names (known names) that you will use for SSL certificates.

4. Other Types of SSL Certificates

There are also Domain SSL, Extended SSL, and Organization SSL certificate types.

• Domain SSL: An SSL certificate service that can be used to protect and secure only a domain name. Single or multiple domain options are also available depending on your need. ‏‏‏‏‏‏

• Organization Validated SSL: Organization Validated SSL is the type of SSL Certificate that turns the browser’s address bar entirely green or displays the name of your organization alongside a green lock. ‏ ‏‏‏‏

• Extended SSL: Extended SSL is the type of certificate service that has more credibility than Domain SSL. The green branded address bar is the most highly recognizable sign of an EV-secured webpage. It shows visitors your website is a safe place to enter their sensitive data. ‏‏‏‏‏‏‏‏

You can try Medianova for 1 month without needing a credit card or any commitments. Your account will be activated automatically. If you need more features or help, our sales team is ready to assist you.

The trial includes important features like Static CDN and Dynamic CDN, which make sure your website content loads faster by delivering it from the closest server. The Web Application Firewall (WAF) lets you create custom security rules to protect your site from harmful traffic. You also get Standard DDoS Protection to keep your website safe from attacks that try to overload it with too much traffic.

The Global Anycast DNS feature improves your site’s DNS performance by directing traffic to the nearest server, which helps reduce loading times. The Purge feature allows you to quickly remove outdated content from all servers so your website shows updates instantly. You can also use page rules to control how your content is cached, forwarded, and secured, giving you more control over how the CDN handles your site.

How to Activate Your Free Trial:

• Fill in the fields for your name, email address, and password.

• Click the Next button.

• Enter the verification code sent to your email.

• For your CDN resource, select Website. Make sure that the Origin URL and the Website URL are different.

• The package will be displayed as Free Trial. Click the Proceed to Purchase button.

• Finally, fill in your billing address and click the Complete Purchase button.

Your Free Trial has now started successfully.

Key Features to Explore:

• Static CDN

• Dynamic CDN

• Web Application Firewall

• DDoS Protection

• Global Anycast DNS

• Purge

Need a Helping Hand?

Product documentation, guides, troubleshooting and API documentation.

Learn how to integrate and optimize your workflows with our detailed API documentation.

Navigating to SSL Management

1. Click on the “CDN → SSL Management” option in the left menu of the panel.

2. The SSL Certificates added to your organization are displayed on this page. If you don’t own an SSL certificate, proceed to Step 5.

Adding a New SSL Certificate

To add a new SSL certificate to your organization:

1. Click on the “Add New SSL” button on the SSL Management page.

2. Fill in the following fields:

   • SSL Name: Specifies the name of the SSL certificate for your organization.

   • Certificate: Upload the CRT file, which enables website verification and secure communication.

   • Private Key: Upload the private key, which is part of the asymmetric encryption used for SSL. This key must be securely stored and is only available on the web server.

   • Certificate Password: Enter the password used to protect the private key.

3. After completing the fields, click the “Add New SSL” button to upload the certificate.

Applying an SSL Certificate to a CDN Resource

To use the SSL certificate you uploaded or to choose the “Shared SSL” option:

1. Navigate to the “CDN → CDN Resources” option in the left menu.

2. Select the specific CDN Resource from the listed resources.

3. Navigate to the SSL tab:

   • For Small and Large resource types, this tab is labeled as “CNAME & SSL”.

   • For Streaming, VOD, and Dynamic resource types, it is labeled as “SSL”.

4. On the SSL tab:

   • Choose the “SNI” option to apply the SSL certificate you uploaded.

   • Or, select the “Shared SSL” option if you don’t own an SSL certificate.

5. Save your changes.

Managing SSL Certificates

In the SSL Management menu, you can also perform the following actions:

• Edit: Allows you to rename the SSL certificate. Note that no other edits are allowed.

• Delete: Prompts a confirmation pop-up before allowing you to delete the certificate.

Supporting Customers with Certificate Chains

If your SSL certificate requires a certificate chain (e.g., Intermediate or Root certificates) and you need to complete it:

• Use the Certificate Chain Completion Tool available at [link-to-tool]. This tool helps you generate and complete the required chain for your certificate.

• After generating the complete chain, upload the updated certificate file using the steps outlined above.

This additional support ensures your SSL configuration is accurate and prevents potential issues caused by incomplete or incorrect chain entries.

The Rate Limiting feature in the Medianova Cloud Panel provides a robust mechanism to control incoming traffic volume, protect your resources from abuse, and optimize overall system performance. By defining request limits and actions, you can effectively manage excessive requests, ensure fair usage, and maintain stability for your CDN services.

Rate Limiting allows you to restrict the number of requests made to your CDN resource within a specified time window (seconds or minutes). It is particularly useful for:

• Preventing abuse: Protect resources from malicious traffic or bots.

• Traffic optimization: Ensure fair access by limiting excessive requests from individual clients.

• Resource protection: Reduce the load on your origin servers and avoid unnecessary bandwidth consumption.

The feature also supports additional actions, IP whitelisting, and configurable HTTP status codes to manage traffic behavior efficiently.

Key Features

1. Customizable Request Limits

   • Define the number of requests allowed within a time window:

     • Seconds: Fine-tune request limits for short intervals.

     • Minutes: Broader control for longer time windows.

2. Rate Limit Options

   • Configure the behavior of rate limits:

     • Burst + No Delay: Allows an initial burst of requests without any delays, ensuring immediate responsiveness.

     • Burst: Allows a burst of requests but applies delays or throttling once the threshold is exceeded.

     • None: Disables burst handling and enforces a strict limit.

3. IP Whitelisting

   • Enable the Whitelist IP Status to exclude specific IP addresses from Rate Limiting rules. This is useful for trusted clients or internal testing purposes.

4. Configurable HTTP Status Codes

   • Choose the response status code when the rate limit is exceeded:

     • 429 Too Many Requests: Indicates the client has sent too many requests within the time window.

     • 529 Site Overloaded: Used when the server is unable to process requests due to excessive load.

5. Action Management (Dynamic CDN Only)

   • Define actions for excessive requests:

     • Block: Reject requests that exceed the rate limit.

     • Challenge: Present a challenge (e.g., CAPTCHA) to validate whether the client is legitimate.

How to Configure Rate Limiting

Follow these steps to configure Rate Limiting for your CDN resources in the Medianova Cloud Panel:

1. Access the Configuration

   • Log in to the Medianova Cloud Panel.

   • Click on the CDN Resources section in the left-hand menu.

   • Select the relevant resource you want to configure.

   • Navigate to the Security tab.

   • Scroll down to the Rate Limiting section.

2. Enable Rate Limiting

   • Locate the Status option.

   • Toggle the Status to On to activate the Rate Limiting feature.

3. Set Request Limits

   • Under the Request Limit section:

     • Specify the maximum number of requests allowed per second or minute.

     • Adjust these values based on your traffic volume and server capacity.

4. Configure Rate Limit Options

   • Select a Rate Limit Option from the following:

     • Burst + No Delay: Allows a temporary spike in requests with no initial delay.

     • Burst: Allows a burst of requests but applies throttling afterward.

     • None: Disables burst handling, enforcing a strict rate limit.

   • If Burst or Burst + No Delay is selected, enter a Burst Value to define the threshold for the burst limit.

5. Whitelist IPs (Optional)

   • To exclude specific IP addresses from Rate Limiting:

     • Toggle the Whitelist IP Status to On.

     • Add the trusted IP addresses to the whitelist.

   • This ensures that trusted clients or internal traffic are not affected by rate limits.

6. Set Status Codes

   • Choose the HTTP status code to be returned when the rate limit is exceeded:

     • 429 Too Many Requests

     • 529 Site Overloaded

7. Define Actions (Dynamic CDN Only)

   • Under the Actions section, select one of the following options:

     • Block: Deny requests that exceed the rate limit.

     • Challenge: Present a challenge (e.g., CAPTCHA) to validate the request.

8. Save Your Configuration

   • Click the Submit button to save your changes.

   • The Rate Limiting rules will now be applied to your selected resource.

Medianova WAF watches all the web traffic coming in, finds any malicious pattern, and thwarts potential threats before they can compromise web assets. It offers pre-defined Managed Rules and enabling these managed rulesets grants immediate protection against a wide range of security threats.

Once you have activated your WAF, you can start configuring your managed rulesets and custom rules based on your requirements.

Enable / Disable a Managed Ruleset

You can toggle the switch beside a managed ruleset to activate or deactivate it.

Enable / Disable a Specific Rule

You can click on the managed ruleset and see the specific rules that are tied to the ruleset. You can toggle the switch beside a specific rule to activate or deactivate it.

Creating a Custom Rule

You can create customized rules using parameters such as user agent, request protocol, request URI, client IP, referrer, and request method. You should enter a rule name, define the appropriate condition, select the WAF action and submit your changes to create a custom rule.

Handle False Positives

If you come across a false positive resulting from a managed rule, you take one of the following actions:

• You can start by activating your WAF in Monitoring-Only mode, to observe underlying traffic, analyze your security posture and derive valuable insights without impeding traffic flow. According to these insights, you can tune your WAF by properly configuring your managed rulesets and custom rules.

• You can disable the associated managed rule. While this approach can help prevent false positives, it does come with the trade-off of diminishing the overall security of the site.

• If a particular rule is responsible for false positives, you may consider to deactivate that individual rule rather than the entire ruleset.

• You can create custom rules for tailored defense and preventing false positives.

Activating the Web Application Firewall (WAF) in the Medianova Cloud Panel enhances your website's security by protecting against potential threats. Whether you’re setting up a new Dynamic CDN Resource or configuring an existing one, the process is straightforward. This guide provides step-by-step instructions to activate WAF, customize its settings, and choose between "Monitoring Only" or full protection modes to safeguard your applications effectively.

2. Click on the “CDN → Create CDN Resource” option on the left menu of the panel if you haven’t created a Dynamic CDN Resource yet. Skip Step 2 and proceed to Step 3, if you have a Dynamic CDN Resource already.

Select Dynamic CDN Resource in the “Start building your CDN” area.

Fill in the requested information and click on the “Create CDN Resource” button.

1. Click on the “Security → WAF” option on the left menu of the panel and press on one of the listed resources to configure and activate your WAF service.

1. You need to change the WAF status to “Monitoring Only” or “On”, to proceed with adding custom rules based on your specific requirements. In the “Monitoring Only” mode, our WAF provides real-time monitoring for potential threats, while allowing all traffic to pass through uninterrupted, providing you with valuable insights into your website’s security posture without affecting its functionality.

2. Next, you can define custom rules based on a wide range of parameters. These are;

• Request Method: Represents the different request methods (GET, POST, PUT, DELETE, etc.) used in the HTTP protocol. It can properly limit the methods of requests to the web application and increase the security of the application.

• Client IP: Represents the IP address of the user connecting to the web application. This information can improve the web application’s ability to verify the origin of requests and perform security checks.

• Referrer: Represents the URL of the previous page that redirects to the web page. This information can help the web application learn more about the origin of its requests and increase security controls.

• Args: Represents the arguments in the HTTP request. These arguments contain the information required for the Web application to function correctly. However, malicious arguments submitted by malicious users can cause security vulnerabilities in the application.

• Request URI: Represents the destination URL of the HTTP request. This information can help the Web application determine how it handles requests and perform security checks.

• Request Protocol: Represents the HTTP protocol used (HTTP/1.1, HTTP/2 etc.). Using the correct protocol version can ensure that the web application functions correctly and performs security checks.

• User Agent: Represents information of the agent (usually a browser) making the HTTP request. This information can help the Web application determine how it handles requests and perform security checks.

5.1. Fill in a “Rule Name” for your custom rule.

5.2 Click on the “Field” dropdown menu and select the parameter you would like to use.

5.3 Choose the corresponding “Operator” and “Value”.

5.4 Press the “And” button if you would like to create a chain of conditions. Please note that current WAF version supports maksimum 3 chain of conditions.

5.5 Select the action you want your WAF to take, when incoming requests match your chain of conditions.

5.6 When you finish entering the required information for your custom rule, press the “Add Rule” button. You can continue to add rules according to your needs.

5.7 When you are done adding rules, please press the “Submit” button.

1. You can edit or delete a custom rule by clicking on the “Edit” and “Delete” icons. When you click on the “Edit” icon, you will see the following screen. Press the “Submit” button after editing your rule.

2. After activating your WAF in “On” or “Monitoring Only” mode, you can monitor metrics by clicking on “Analytics → WAF” option on the left menu of the panel. Select your WAF resource to display the following metrics;

• Threats: The number of requests made to the WAF rules among the requests made to the website.

• Top 10 Client IPs: User IP addresses from which requests plugged into WAF rules come from.

• Top 50 Request Uri: Addresses where requests stuck in WAF rules are made.

• Top 50 User Agent: Device information from which requests plugged into WAF rules are made.

• Rule: Information on which rule the requests stuck in WAF rules are stuck on.

• Last 300 Activity Log: Detailed information of the last 300 requests stuck in WAF rules.

Overview

A Web Application Firewall (WAF) provides an essential layer of security for your website, protecting it from malicious attacks by analyzing incoming traffic and blocking harmful requests. To efficiently manage this security layer, it is crucial to regularly monitor and analyze the WAF’s analytics data.

Once your WAF is activated in either "On" or "Monitoring Only" mode, you can access detailed metrics by navigating to the Analytics → WAF section in the panel. This data provides you with valuable insights into the security status of your website, enabling you to make informed decisions about how to enhance your protection.

This document explains the key metrics and charts available in the WAF analytics dashboard, and how to interpret and use them effectively.

Dashboard Visualizations

The WAF analytics dashboard also includes various charts and tables that make it easier to understand and interpret the data. These visualizations help you quickly spot trends, patterns, and anomalies in your website's traffic and security.

1. Attack Histogram

The Attack Histogram displays the number of attacks over time, helping you identify patterns and trends in security incidents. This chart can be filtered by URL to provide a more granular view of attacks targeting specific pages or resources on your website.

2. Threats

The Threats metric represents the number of requests that have triggered WAF rules relative to the total number of requests made to your website. This data helps you understand the volume of potentially malicious traffic your site is receiving and how effective your WAF is at blocking harmful requests.

When analyzing this metric, pay attention to sudden spikes in threat volume, as they may indicate an attack or a change in traffic patterns. Tracking the Threats metric over time will allow you to gauge the overall effectiveness of your security rules and identify if any adjustments are necessary to improve threat detection and mitigation.

The Threats Table breaks down threat data into several time periods:

• Total: The total number of threats detected since the WAF was activated.

• Today: The number of threats detected today.

• This Month: The number of threats detected in the current month.

• Last Month: The number of threats detected in the previous month.

3. Top 10 Client IPs

The Top 10 Client IPs table displays the IP addresses responsible for triggering the most WAF rules. This metric helps identify potential sources of malicious traffic or attackers. By reviewing this data, you can take proactive measures, such as blocking or rate-limiting suspicious IPs. It also helps recognize patterns, such as bot-driven traffic or targeted attacks from specific regions or entities. The accompanying Pie Chart provides a visual breakdown of these IPs, making it easier to identify high-risk sources and take swift action to mitigate potential threats.

4. Top 50 Request URIs

The Top 50 Request URIs table displays the URLs on your website most frequently targeted by requests that trigger WAF rules. This metric helps identify which parts of your site are under the most attack, allowing you to pinpoint areas that may be more vulnerable. By analyzing the Request URIs, you can detect patterns in attack vectors, such as specific endpoints or resources being targeted, and adjust your security measures accordingly. If certain URLs are consistently attacked, you may consider implementing more tailored WAF rules to strengthen protection for those areas.

5. Top 50 User Agents

The Top 50 User Agents table provides insight into the devices and browsers generating requests that are being blocked by WAF rules. This data can help you identify anomalies in traffic, such as attacks coming from unusual user agents, which may indicate automated bot traffic.

6. Rule

The Rule metric indicates which specific WAF rule is triggered by incoming requests. This helps assess the effectiveness of each rule in detecting and mitigating threats. By analyzing which rules are most frequently triggered, you can identify patterns in attack types and adjust your rule configuration accordingly. If a rule is triggered too often, it may indicate false positives or that the rule needs refinement to better suit your site's needs.

The Rule table displays the most frequently triggered WAF rules. This table allows you to evaluate the performance of each rule and understand which threats are being blocked most effectively. Frequent triggers suggest the rule is successfully mitigating a particular type of attack, but if the rule is ineffective, it may require adjustments.

7. Last 300 Activity Log

The Last 300 Activity Log displays detailed information on the most recent 300 requests flagged by WAF rules. This log allows you to dive deeper into recent security incidents, providing crucial insights for further investigation and threat mitigation.

Conclusion

By regularly monitoring these WAF analytics metrics and reviewing the dashboard charts, you gain valuable insights into the security of your website. This data allows you to detect potential threats early, identify patterns in malicious traffic, and fine-tune your WAF rules to ensure maximum protection.

For further assistance or to customize your WAF settings, please refer to the help section in the panel or contact support.

IP Restriction ACL, short for Access Control List, regulates access by controlling which IP addresses are allowed or denied access to specific network resources.

This type of ACL typically offers two main options:

1. Whitelist: In this mode, only devices with specific IP addresses are allowed access to designated resources. IP addresses added to the whitelist are granted access, while all others are denied.

2. Blacklist: In contrast, devices with IP addresses listed in the blacklist are denied access to designated resources, while all other devices are allowed access.

Multiple IP addresses can be added to either the whitelist or the blacklist, depending on the desired access control policy. For example, you might whitelist IP addresses belonging to trusted partners or blacklist IP addresses associated with malicious activity.

However, it's important to note that you cannot use the whitelist and blacklist options simultaneously. They are mutually exclusive. You must choose one mode or the other, as they serve conflicting purposes.

This type of IP Restriction ACL is commonly employed to enhance network security by restricting access to critical resources and mitigating unauthorized access attempts.

To access the IP Restriction ACL setting in the Medianova Cloud Panel, follow these steps:

1. Start by clicking on CDN in the left-hand menu, then select CDN Resources from the submenu.

2. From the list of CDN Resources, choose the one for which you wish to configure the IP Restriction ACL setting.

3. Navigate to the Security tab within the selected CDN Resource.

4. Within the Security tab, you'll find the IP Restriction ACL setting.

5. When you enable IP Restriction ACL, two options will appear: Whitelist and Blacklist.

6. If you want to allow specific IP addresses and block others, select Whitelist. Enter the allowed IP addresses and click on the + icon.

7. If you want to block specific IP addresses and allow others, select Blacklist. Enter the blocked IP addresses and click on the + icon.

8. Click on the Save Changes button.

Medianova's Static CDN service is a tailored solution designed for websites and applications to efficiently deliver static content, focusing on elements like images, style sheets, and script files. The primary goal is to enhance the speed and effectiveness of content delivery by strategically distributing static assets across a global network of servers. Leveraging this globally distributed infrastructure, the service ensures that end-users receive content from the nearest server, thereby minimizing latency and optimizing page loading times.

The Static CDN by Medianova boasts key features, including global accessibility, high availability, and seamless scalability to accommodate varying levels of web traffic. To integrate this service, users can sign up for a Medianova account, configure CDN settings within the platform, and update the URLs of their static assets to point to the CDN. This straightforward integration empowers content providers to enhance website performance and deliver an optimized user experience.

For advanced configurations, users can set up a custom domain for a branded experience, enable SSL/TLS support for secure content delivery, and fine-tune compression settings to optimize file sizes. The service also provides monitoring and analytics tools, offering detailed usage statistics and real-time monitoring to ensure optimal performance and user satisfaction.

In summary, Medianova's Static CDN is a comprehensive solution catering to the specific needs of content providers seeking to accelerate static content delivery, improve website performance, and elevate the overall user experience on a global scale.

Geo-Blocking allows you to control which countries can directly access your content. You can restrict the countries you choose from the list by dragging them to the whitelist and blacklist boxes. You can also define certain IP addresses to be in the whitelist and blacklist from the IP Restriction section.

While geo-blocking is often used as a blocking tool due to copyrights and licenses, it can also be used to enforce different pricing policies for end-users. Another common use is to prevent malicious traffic and illegal applications such as gambling and betting on the internet.

How to manage Geoblocking on Medianova Cloud Panel

2. You can reach the Geoblocking setting by clicking on the CDN Resource you would like to edit by following the CDN → CDN Resources path on the left side of the panel and navigating to Security tab.

3. After turning on the status of the Geoblocking setting, you can carry out the operation by moving the countries you want from the country list on the left to the whitelist or blacklist pane.

4. You can update your whitelist and blacklist and save changes any time.

1. You can also perform the same operation over IPs from the IP Restriction section at the bottom of the page.

Large CDN Resource is the type of resource you should use to serve your large content such as video, music, zip, exe files.

2. Click on the “CDN > Create CDN Resource” option on the menu on the left of the panel screen that will open after logging in.

3. On the next screen, select Large & VOD Streaming CDN Resource from the “Start building your CDN” field. The VOD option can be used to transcode video content (mp4 files..) to streaming protocols.

4. Make a selection between Large or VOD CDN Resource options according to your needs. Fill in the requested information for the selected CDN Resource.‏‏‏‏‏‏‏‏

   1. Source of Your Files (when CDN Storage is selected): CDN Storage: Select this option to host your content on Medianova servers and serve it to the end user with the Origin Push method.

      FTP Password: It is the password you will set for the FTP user to be created to upload your content.

      FTP Password Confirmation: Enter the FTP password again.

      CDN Resource Label: In this field, a label describing your CDN Resource is entered.

The IP list required for your CDN (Content Delivery Network) configuration contains the server addresses necessary for your CDN to be configured correctly and securely. This IP list should be configured in collaboration with your CDN provider. Please ensure that these IP addresses are accurately communicated to your CDN provider.

This list may include specific IP blocks or ranges.

This list presents individual IP addresses in a text format. Each line may contain a single IP address.

This list is presented as a CSV file containing IP blocks or ranges.

There are two different methods that can be preferred while creating a Small CDN Resource: Origin Pull and Origin Push.

• The Origin Pull Method: It requires a domain or an IP address that belongs to your server where you store your contents. Your contents will be pulled from the source URL and cached at the edge server nearest to the end-user.

• The Origin Push Method: It caches contents similar to the origin pull method. The only difference is the source of your content. Your contents will be stored on Medianova Cloud Storage and it will act as an origin to the Small CDN Resource.

How to Create a Small CDN Resource?

2. In the next screen, Small CDN Resource is selected from the “Start building your CDN” field.

3. Fill in the requested information for Small CDN Resource.

• Source of Your Files (when My Origin is selected):

  • My Origin: Select this option if your CDN Resource will use Origin Pull method.

  • Origin URL: In this field, the origin URL from which the content will be extracted is specified. (http(s)://www.example.com).

  • CDN Resource Label: In this field, a label describing your CDN Resource is entered.

    ‏‏‏‏‏‏‏‏

• Source of Your Files (when CDN Storage is selected):

  • CDN Storage: Select this option to host your content on Medianova servers and serve it to the end user with the Origin Push method.

  • FTP Password: It is the password you will set for the FTP user to be created to upload your content.

  • FTP Password Confirmation: Enter the FTP password again.

  • CDN Resource Label: In this field, a label describing your CDN Resource is entered.

    ‏‏‏‏‏‏

The Advanced Origin Settings feature enables users to set up intricate rules for origin configuration, providing a highly customizable and efficient way to optimize content routing. This functionality supports flexible routing by allowing you to define specific matching criteria for URIs, protocols, domains, ports, and more.

Key Features

• URI Matching Criteria: Configure rules to match specific file extensions or directories.

• Protocols: Choose the protocol (HTTP, HTTPS, or same as request) to route traffic.

• Domain/IP Settings: Define specific domains or IPs for origin requests.

• Port Configuration: Specify HTTP and HTTPS ports to communicate with the origin server.

• Host Header Customization: Set custom host headers to align with origin requirements.

• Priority Levels: Assign priority to rules, ensuring the correct settings are applied in case of overlaps.

How to Configure Advanced Origin Settings

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Origin Settings tab.

4. Navigate to the Advanced Origin Settings section in the Medianova Cloud Panel.

1. Click the Add button to open the configuration popup.

2. Fill in the following fields:

   • URI Match Mode: Select the matching mode for URIs (e.g., exact match, prefix, or regex).

   • URI Match Rule: Define the URI pattern based on the selected mode.

   • Protocols: Choose between HTTP, HTTPS, or Same as Request to determine how the traffic should be routed.

   • Domain or IP: Enter the domain or IP address of the origin server.

   • HTTP Port: Specify the HTTP port to use for connections.

   • HTTPS Port: Specify the HTTPS port to use for secure connections.

   • Host Header: Provide a custom host header if required for the origin server.

   • Priority: Assign a priority level to this rule to determine its precedence in case of multiple matching configurations.

3. Click the Add button.

4. Click the Submit button.

Understanding DDoS Attacks

Distributed Denial of Service (DDoS) attacks involve overwhelming a target system or network with a flood of traffic, rendering it unavailable to users.

How Medianova DDoS Protection Works

Mitigation Strategies

A variety of mitigation strategies are integrated into Medianova's DDoS protection. From Rate limiting to IP blocking or Geoblocking, our service ensures minimal disruption to your services.

Always-on DDoS Defense

Your DDoS defense is always on. You don’t need an extra activation process to protect your web assets against common attack types such as;

• DNS Query Floods

• SlowLoris

• HTTPS GET

• HTTPS POST, and more.

Anycast DNS Infrastructure

Our Anycast DNS network distributes thousands of requests across multiple servers that might overwhelm a single server and mitigates DDoS attacks.

IP Protection

You can mitigate the likelihood of DDoS threats preemptively by concealing your origin IP address before an attack can be initiated.

Origin Shield

Medianova provides you an extra layer of security for your origin and limits its exposure to possible DDoS attacks with our Secure Cloud.

Web Application Firewall (WAF) Integration

By combining DDoS Protection with WAF, Medianova provides a multi-layered defense mechanism, offering protection not only against DDoS attacks but also against application layer threats.

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.

Creating a Medianova CDN Resource

To get started with Medianova CDN, follow these steps:

2. Click on the Create CDN Resource tab in the left menu.

3. Choose any resource type and fill in the necessary fields.

4. Create a resource and configure the necessary settings.

5. The resource you created will be in a "pending" status. Below is information about the resource statuses:

Configuration

The CDN URL and the ORIGIN URL below are examples.

Enlarges the table by opening it in a full screen dialogOpen

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:

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.

The Origin SNI Request feature ensures that Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connections to your origin server use the correct domain name during the handshake process. This is achieved by sending the Server Name Indication (SNI) extension as part of the connection request. The SNI is crucial when your origin server hosts multiple domains under the same IP address, as it allows the server to present the appropriate SSL certificate for the requested domain.

This feature is particularly important for dynamic content delivery, where secure connections are established frequently and need to support multiple domains efficiently. By enabling Origin SNI Request, you enhance the compatibility of your CDN with your origin server, ensuring smooth SSL/TLS connections.

How to Configure Origin SNI Request

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Origin Settings tab.

4. Navigate to the Origin SNI Request section in the Medianova Cloud Panel.

5. Enable the Origin SNI Request setting by toggling it to On.

1. Provide the required Origin SNI Request Domain:

• Enter the domain name for which SSL/TLS connections should be established.

• Ensure the domain corresponds to a valid SSL certificate on the origin server.

1. Click Submit to save the configuration.

The Origin Response Timeout setting in the Medianova Cloud Panel allows you to control how long the system will wait for a response from your origin server before considering the request as failed. By adjusting this timeout, you can manage server response times more effectively, ensuring a better user experience and reducing unnecessary delays.

Key Features

• Customizable Timeout Duration Set a specific time (in seconds) that the system will wait for a response from the origin server.

  • Min: 5 seconds

  • Max: 300 seconds

• Efficient Request Handling Define a timeout that suits your needs, balancing between faster responses and allowing enough time for slower origin servers.

• Improved User Experience Avoid excessive wait times for users by setting a reasonable timeout value to handle delayed responses effectively.

How to Configure Origin Response Timeout

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Origin Settings tab.

4. Navigate to the Origin Response Timeout section in the Medianova Cloud Panel.

1. Set the Timeout Duration: In the Origin Response Timeout section, set the timeout value between 5 seconds and 300 seconds, according to your needs.

2. After adjusting the timeout, click Save to apply the new settings.

By configuring the Origin Response Timeout, you can optimize the time the system waits for a response, ensuring that requests are handled efficiently without unnecessary delays.

The Rewrite Origin URLs feature allows users to define rules for rewriting origin URLs. This provides enhanced control over how requests are routed and redirected, ensuring flexibility and optimization in URL management.

Key Features

Match Mode Options: Select specific modes to match URL patterns for rewriting.

Origin URI: Specify the original URI that triggers the rewrite rule.

Target URI: Define the new URI to which requests should be redirected. Priority Settings: Assign priorities to rules to control their execution order.

How to Configure Rewrite Origin URLs

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Origin Settings tab.

4. Navigate to the Rewrite Origin URLs section in the Medianova Cloud Panel.

1. Click the Add button to open the configuration popup.

2. Fill in the required fields:

   • Match Mode: Choose from the following options:

     • All files: Apply the rule to all files.

     • Path: Match a specific path.

     • Full Path: Match the exact full path of the URL.

     • Wildcard: Use wildcards for broader matching patterns.

   • Origin URI: Enter the URI that should be rewritten.

   • Target URI: Provide the URI where requests should be redirected.

   • Priority: Assign a priority to this rule to determine its execution order when multiple rules are defined.

3. Click the Add button.

4. Click the Submit button.

If you wish to restrict access to your CDN Resource exclusively through links on your website, you have the option to establish hotlink protection for that specific CDN Resource. The functionality of hotlink protection relies on the "Referer:" header present in each HTTP request.

Hotlink protection is a security feature to prevent unauthorized use of hosted media files, such as images, videos, or other static content. The term "hotlinking" refers to the practice of directly embedding or linking to these files from external websites, without the owner's permission.

Hotlink protection works by checking the "Referer" header in the HTTP request. The "Referer" header indicates the URL of the webpage making the request. When hotlink protection is enabled, the server verifies whether the request is coming from an allowed source (whitelisted domains) or a restricted source (blacklisted domains). If the request is from an unauthorized source, the server can take various actions, such as blocking access, redirecting to a specified page, or serving a placeholder image.

This feature helps website owners and content providers control how their resources are used, preventing others from using their bandwidth and server resources to display content on external sites without permission. Hotlink protection is particularly useful for conserving bandwidth, reducing server load, and maintaining control over the distribution of digital assets.

This feature can be conveniently configured by selecting your CDN Resource and navigating to the Security menu.

Canonical Name (CNAME) is the nickname given to URL records.

Instead of the CDN URL provided to you by Medianova, you can use a URL determined by you. We have explained below for you how to set CNAME on Medianova Cloud panel.

2. You can reach the settings screen by clicking on the Streaming Resource you want to edit by following the CDN > CDN Resources path on the left side of the panel screen that will open after logging in.

• If you are using SSL, in order to use CNAME, you must define the relevant information under the SSL tab at the bottom of the page.

• For the CDN configuration process, you have to replace the source code that contains your Origin URL with the CDN URL.

The Error Status Code Cache Expiration feature in the Medianova Cloud Panel allows you to cache specified error codes (such as 404, 500, etc.) for a defined duration. By doing so, you can control how long error responses are stored in the CDN cache, reducing the number of requests sent to the origin server. If you don't want certain error codes to be cached, simply remove their definitions, and requests for those error codes will be sent directly to the origin server. However, if the content has already been cached, the cache duration will remain in effect until it expires.

Key Features

• Cache Error Status Codes: You can define a set of error codes (e.g., 404, 500, etc.) and specify a cache duration for each. This helps in reducing the load on your origin server by caching error responses for a certain period.

• Removal of Caching Definition: If you remove a cached error status code definition, requests for that error will bypass the CDN cache and be sent directly to the origin server. However, cached content will not be affected immediately and will remain in the cache until the cache duration expires.

How to Configure Error Status Code Cache Expiration

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Caching tab.

4. Navigate to the Error Status Code Cache Expiration section in the Medianova Cloud Panel.

1. Click the Add button to create a new definition.

   • Cache Time: Specify the cache duration for the error code (in seconds).

   • Status Code: Enter the HTTP status code(s) that you want to cache (e.g., 404, 500, etc.).

   • Add Multiple Definitions: You can add multiple error status codes and their respective cache durations by clicking the Add button repeatedly.

2. Once all necessary error codes and cache times are defined, click Submit to apply the changes.

The Etag Verification feature in the Medianova Cloud Panel helps ensure the consistency and accuracy of cached content by validating it using the Etag header. When enabled, the system checks the Etag value sent by the origin server to determine if the cached version of a resource is still valid or needs to be refreshed. This ensures that users always receive the most up-to-date version of a resource, reducing the chances of serving stale or outdated content.

Key Feature

• Etag Validation:

  • When enabled, the Etag header is used to verify cached content, ensuring that the content served to users matches the most recent version from the origin server. This prevents issues where outdated or mismatched content might be delivered.

How to Enable Etag Verification

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Caching tab.

4. Navigate to the Etag Verification section in the Medianova Cloud Panel.

5. Enable Etag Verification: Toggle the Etag Verification setting to On to enable it. This will allow the system to validate the cached content based on the Etag header.

6. Once enabled, click Submit to apply the changes.

1. Identify Static Assets:

Identify the static assets on your website that can benefit from CDN acceleration. These may include images, stylesheets, scripts, and other static files.

1. Update URLs in HTML Code:

Replace the URLs of static assets in your HTML code with the corresponding CDN URLs. Update the "src" or "href" attributes of image tags, script tags, link tags, etc., to point to the CDN.

HTML

• Before CDN Integration →

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

• After CDN Integration →

<imgsrc="https://CDN_URL/images/example.jpg" alt="Example Image">

1. Update CSS File References:

If your stylesheets are hosted locally, update the references to these files in your HTML to point to the CDN. Similarly, replace any background images or other assets within your CSS files.

CSS

• Before CDN Integration →

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

• After CDN Integration →

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

1. Update JavaScript File References:

If your website includes JavaScript files, update references to these files to use the CDN URLs. This ensures that scripts are served through the CDN for improved performance.

HTML

• Before CDN Integration →

<script src="/scripts/example.js"></script>

• After CDN Integration →

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

1. Consider Relative Paths:

If your URLs are currently specified with relative paths, ensure that they remain functional after CDN integration. Adjust paths as needed to maintain proper file references.

1. Verify Links and Resources:

Review your website thoroughly to confirm that all links and resources are properly updated to use the CDN. Check for any broken links or missing assets.

1. Update Content Management Systems (CMS):

If your website uses a CMS (Content Management System) such as WordPress, update any relevant settings or plugins to ensure that URLs are correctly replaced for CDN delivery.

1. Define IPs in your Firewalls:

1. Test Across Environments:

Test your website across different environments, including staging and production, to ensure that CDN integration works seamlessly and doesn't introduce any issues.

1. Monitor and Optimize:

After integration, monitor the CDN's performance using analytics tools provided by your CDN provider. Optimize as needed for improved content delivery and user experience.

1. Update SEO Considerations:

Consider the impact of CDN integration on SEO. Ensure that search engines are aware of the change and update sitemaps and robots.txt accordingly.

The Browser Cache Rule feature in the Medianova Cloud Panel allows you to configure caching behavior for different types of resources. By setting up specific rules for browser caching, you can optimize content delivery, reduce load times, and ensure the most efficient use of cache for various resource types.

Key Features

• Flexible Cache Type Options You can create caching rules based on different criteria, ensuring the correct content is cached efficiently:

  • All Files: This rule applies to all files, regardless of their type or location.

  • Full Path: Apply the caching rule to files based on their exact full URL path.

  • Directory: Apply the caching rule to all files within a specific directory.

  • File Extension: Apply the caching rule based on the type of file (e.g., images, JavaScript, CSS) by specifying file extensions like .jpg, .js, .css, etc.

• Cache Priority Set the priority for each cache rule to determine which resources are cached first. Prioritize critical resources (e.g., images, JavaScript) over less important ones.

• Cache Mode Options Define how each resource should be cached by the browser:

  • Origin: The resource is fetched and cached from the origin server.

  • No Cache: The resource will not be cached at all, and will always be fetched from the origin server.

  • Cache: The resource is cached in the browser for the specified duration, improving performance for subsequent requests.

• Apply the HTML/JSON Files You can apply the cache rule specifically to HTML and JSON files by enabling or disabling this setting:

  • On: The caching rule will be applied to HTML and JSON files.

  • Off: The caching rule will not apply to HTML and JSON files.

How to Configure Browser Cache Rule

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Caching tab.

4. Navigate to the Browser Cache Rule section in the Medianova Cloud Panel.

1. Click on the Add button to create a new cache rule.

   • Configure Cache Rule Settings:

     • Type: Choose the type of cache rule you want to apply:

       • All Files: Applies to all files.

       • Full Path: Applies to files based on their exact URL path.

       • Directory: Applies to all files within a directory.

       • File Extension: Applies based on file extensions like .js, .css, .jpg, etc.

     • Priority: Set the priority (e.g., High, Medium, Low) for this cache rule to manage which files are cached first.

     • Cache Mode: Select the cache mode:

       • Origin: The resource is cached from the origin server.

       • No Cache: The resource is not cached.

       • Cache: The resource is cached in the browser for a set duration.

     • Apply the HTML/JSON Files:

       • On: Enable this option to apply the rule to HTML and JSON files.

       • Off: Disable this option to exclude HTML and JSON files from this cache rule.

2. Once you've configured the browser cache rule, click Submit to apply the changes.

By configuring the Browser Cache Rule, you can control how different file types are cached, ensuring that critical resources are loaded faster and less important resources are handled according to your specifications. The option to apply or not apply to HTML/JSON files provides further flexibility in caching strategies.

The Redirect Handle From Origin setting in the Medianova Cloud Panel provides enhanced control over how redirects are managed for your origin server. Enabling this setting allows you to customize specific parameters related to redirection, ensuring a more precise and tailored redirect process.

Key Features

1. 3xx Error Codes Configuration

   • Manage and customize responses for HTTP status codes in the 3xx range (e.g., 301, 302, 307).

   • Fine-tune redirect behaviors to meet your specific requirements.

2. Request Headers Management

   • Specify which request headers should be included or excluded during the redirect process.

   • Maintain consistency in header data passed to your origin server.

3. Additional Headers Handling

   • Add or modify custom headers that need to be appended during redirection.

   • Ensure compatibility with client or server-specific needs.

How to Enable Redirect Handle From Origin

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Origin Settings tab.

4. Enable this setting.

5. Fill in the required fields.

   • Handle Origin Redirection Error: Select which HTTP status codes (301, 302, 303, 307, 308) to handle for origin redirections. You can choose one or multiple options depending on the behavior you want to implement.

   • Request Header Key: Specify the name of the request header you want to manage during the redirection process.

   • Request Header Value: Provide the value for the corresponding request header key.

   • Add Header Key: Specify the name of the custom header to be appended during the redirection.

   • Add Header Value: Provide the value for the custom header key to ensure it is correctly appended.

6. Click the Add button.

7. Click the Submit button.

The Edge Cache Expiration setting in the Medianova Cloud Panel allows you to control how long content will be cached on the CDN edge servers before it expires. This setting helps optimize performance by ensuring that frequently accessed content is served quickly, while still allowing for up-to-date content retrieval when needed.

Key Features

• Cache Type This cache type ensures that content is cached both at the edge servers and the origin server. The content will be dynamically retrieved from the origin server when necessary, providing flexibility and up-to-date content.

• Cache Time Configuration Set the expiration time for content cached on the edge servers. You can define specific cache expiration times based on your content's needs. When both edge and origin cache settings are used, the system will prompt you to define the cache expiration for each.

How to Configure Edge Cache Expiration

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Caching tab.

4. Navigate to the Edge Cache Expiration section in the Medianova Cloud Panel.

1. Select Cache Type: Choose edge-origin-dynamic as the cache type.

2. Define Cache Expiration Time: When both edge and origin cache settings are enabled, you will be prompted to specify the cache expiration time for both. Set the expiration time according to your needs.

3. Once you’ve configured the expiration time, click Save to apply the changes.

By setting the Edge Cache Expiration, you can ensure that content is efficiently cached on the edge servers while still allowing for timely updates from the origin server when required.

The Query String Caching feature in the Medianova Cloud Panel provides enhanced control over how query strings are cached by the CDN. When enabled, the CDN caches each query string separately, allowing you to fine-tune caching behavior for different variations of the same URL based on query string parameters.

Key Features

• Enable Query String Caching: When Query String Caching is enabled, every query string variation of a URL will be cached separately. This ensures that resources with different query strings are treated as distinct cached items, allowing for more precise control over caching.

• Ignore Specific Query Strings: When this option is enabled, you can specify query strings that you don’t want to cache separately. These query strings will be ignored in the caching process, and the CDN will treat requests with these query strings as if they don't exist.

  • How It Works:

    • After enabling this option, a field will appear where you can enter the specific query strings you wish to ignore.

    • You can add multiple query strings by clicking the + button.

    • Once set, requests with the specified query strings will not result in separate cached versions.

• Cache Specific Query Strings Only: When enabled, you can specify a list of query strings that should be cached separately. Only requests with these specific query strings will create distinct cached versions.

  • How It Works:

    • After enabling this option, a field will appear where you can enter the query strings you want to cache separately.

    • You can add multiple query strings by clicking the + button.

    • Once set, only requests with these query strings will be cached separately, while others will be treated as the same resource.

Important Note:

• Mutual Exclusivity: Both the Ignore Specific Query Strings and Cache Specific Query Strings Only options cannot be enabled at the same time. Only one of these options can be active at any given time.

How to Configure Query String Caching

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Caching tab.

4. Navigate to the Query String Caching section in the Medianova Cloud Panel.

1. Choose Caching option.

   1. Ignore Specific Query Strings: Enable this option if you want to ignore specific query strings and not cache them separately. Enter the query strings you want to ignore in the provided field. Click the + button to add multiple query strings.

   2. Cache Specific Query Strings Only: Enable this option if you want to cache only specific query strings separately. Enter the query strings you want to cache separately in the provided field. Click the + button to add multiple query strings.

2. After configuring the query string caching settings, click Submit to apply the changes.

By configuring the Query String Caching settings, you gain granular control over how query string variations of your resources are cached, optimizing caching strategies based on your specific needs.

Search engines like Google or Yahoo deploy automated bots that routinely scan websites, seeking out information such as blogs, images etc. and they decide what should be included in their indexes. A robots.txt file provides these search engines with the necessary information to properly crawl and index a website's content.

The robots.txt file empowers website owners to exert control over the crawling and indexing process, offering several valuable advantages such as SEO Optimization and Traffic Control. Robots.txt allows you to prioritize which pages you want search engines to focus on.

This can enhance your website's SEO (Search Engine Optimization) efforts by ensuring that the most valuable and relevant content gets indexed and ranked prominently in search results. Furthermore, by specifying which parts of your site should or should not be crawled, you can manage the flow of search engine bot traffic. This helps prevent the bots from overwhelming your server with excessive requests, ensuring a smoother user experience for your visitors.

To access the robots.txt setting in the Medianova Cloud Panel, follow these steps:

1. Start by clicking on 'CDN' in the left-hand menu, then select 'CDN Resources' from the submenu.

2. From the list of CDN Resources, choose the one for which you wish to configure the robots.txt setting.

3. Navigate to the 'Caching' tab within the selected CDN Resource.

4. Within the 'Caching' tab, you'll find the robots.txt setting. Selecting “Enable” option activates the Medianova Robots.txt file, allowing indexing of all files.

5. Alternatively, selecting the 'Origin' option activates the Robots.txt file located on the origin server for indexing all files."

The Shared Cache feature in the Medianova Cloud Panel allows you to define a Domain Cache Key that enables the use of the same cache structure across different accounts. This feature is useful when you want multiple accounts or domains to share the same cached content, optimizing content delivery and reducing redundancy. The cache structure is determined based on the defined Domain Cache Key, ensuring that the same cached data is available to all relevant accounts.

Key Features

• Domain Cache Key: The Domain Cache Key is defined to allow multiple accounts or domains to share the same cache. This reduces the need to cache identical content separately for each account, improving caching efficiency.

• Cache Sharing Across Accounts: By setting the cache to "Shared", you can enable different accounts to access the same cache, ensuring faster content delivery and reduced load on the origin server.

Status Options:

• Default (Default Setting): This is the default status for the cache key. The cache is not shared across accounts, and each account has its own separate cache structure.

• Share: When set to "Share", the Domain Cache Key will allow multiple accounts to use the same cache structure, enabling shared caching of content.

How to Configure Shared Cache

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Caching tab.

4. Navigate to the Stale Cache section in the Medianova Cloud Panel.

5. Set the Cache Status:

   • To enable shared cache, select the Share option.

   • To keep the cache separate, leave it set to the Default option.

6. Save Your Settings: Once you've selected the desired cache status, click Submit to apply the changes.

Websites usually consist of applications, images, fonts, and many other resources hosted on different servers on the internet. While CORS (Cross-Origin Resource Sharing) stands for cross-origin resource sharing, it is a mechanism that allows such resources hosted on different servers to be received with additional domain names. It aims to stretch the restrictions of Same-Origin-Policy (SOP), which prevents content delivery from different origins by using an additional domain name due to security measures, with legal methods.

Medianova CDN supports this feature for all CDN Resource types. You can manage this feature, which allows content delivery from different origin servers with the same domain name, by following the steps below.

2. You can reach CORS Header setting by clicking on the CDN Resource you would like to edit by following the CDN > CDN Resources path on the left side of the panel screen and navigating to Headers tab.

1. The domains you add will be listed as shown below.‏‏‏‏‏‏‏‏

1. If the CORS Header feature is disabled, content cannot be received from different sources with different domain names. When content is requested from different sources, the content will not be served and will appear as a CORS error on the Development Tools console.

2. Activating CORS Header allows content to be received from different sources over additional domains. It is possible to define more than one additional domain. You can delete any previously defined additional domain name, as well. If no value is entered in the domain name field while enabling CORS header, the default setting is being set to *, which means requests from all sites and domains will be allowed. This operation is not recommended as it may create security vulnerabilities.

3. It may take a few minutes for the feature to be active, after adding domains and submitting the changes by clicking on the button.

The Range-Based Caching feature in the Medianova Cloud Panel allows caching of partial content based on byte ranges. This is particularly useful for large files, as it improves efficiency by serving only the requested portions of a file, reducing unnecessary data transfer and load on the origin server.

Key Features

• Partial Content Caching: Caches specific byte ranges of a file instead of the entire file, enabling efficient delivery for large media files or downloads.

• Optimized Bandwidth Usage: Only the requested portions of a file are delivered, minimizing bandwidth consumption and improving response times.

• Customizable Byte Ranges: Define the maximum size of byte ranges to cache, tailoring the caching behavior to suit your resource requirements.

How to Configure Range-Based Caching

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section from the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to enable range-based caching.

3. Click on the Caching tab.

4. Navigate to Range-Based Caching Settings: In the resource settings panel, locate the Range-Based Caching section.

5. Enable Range-Based Caching: Toggle the setting to On to activate range-based caching.

6. Select Byte Range Size:

   • From the dropdown menu, select the desired byte range size that fits your caching needs.

   • The chosen size determines the maximum byte range to cache for each partial content request.

7. Submit Your Settings: Once configured, click Submit to save and apply your changes.

The Stale Cache feature in the Medianova Cloud Panel allows you to serve stale (previously cached) content when certain HTTP error codes or an "Updating" status is encountered. This ensures uninterrupted availability of content during temporary origin server issues or while content is being updated.

Key Features

• Maintain Availability: Serve cached content even when the origin server experiences temporary issues or returns specific error codes.

• Customizable Error Triggers: Select which HTTP error codes or the "Updating" status should activate the use of stale cached content.

• Improved User Experience: Reduces downtime and ensures users continue to access content even during backend disruptions.

Supported Triggers

You can configure the system to serve stale cached content when any of the following statuses are detected:

• Updating: Triggered when content is in the process of being updated.

• HTTP_500: Internal Server Error.

• HTTP_502: Bad Gateway.

• HTTP_503: Service Unavailable.

• HTTP_504: Gateway Timeout.

• HTTP_403: Forbidden.

• HTTP_404: Not Found.

• HTTP_429: Too Many Requests.

How to Configure Stale Cache

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Caching tab.

4. Navigate to the Stale Cache section in the Medianova Cloud Panel.

5. Activate the Stale Cache option to configure the settings.

6. Select Error Triggers:

   • Choose the HTTP error codes (e.g., 500, 502, 503, etc.) or Updating status that will trigger the use of stale cached content.

   • Multiple triggers can be selected simultaneously.

7. Click Submit to apply your configurations.

The X-CDN Header feature in the Medianova Cloud Panel allows you to include the X-CDN header in the response for static content. This header signifies that the content is being delivered through the CDN, helping with performance tracking, debugging, and analytics.

Key Features

• Indicates CDN Usage: When enabled, the X-CDN header is added to the response, confirming that the content is served from the CDN edge servers.

• Useful for Static Content: This is especially helpful for static resources like images, JavaScript files, and CSS files, providing visibility into the CDN usage for static content.

How to Configure Custom Headers

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section in the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to configure custom headers.

3. Click on the Headers tab.

4. Enable X-CDN Header: Locate the X-CDN Header section and toggle the setting to On.

5. Submit Your Configuration: Click the Submit button to save and apply your changes.

The Custom Header feature in the Medianova Cloud Panel allows you to define, modify, or manage HTTP headers for requests, providing greater flexibility and control over how headers are handled.

Key Features

• Customizable Headers: Add, modify, hide, or delete headers to tailor request handling based on your requirements.

• Flexible Management: Define specific key and value pairs for each header action.

• Batch Configuration: Add multiple headers using the + button, streamlining the configuration process.

Available Header Actions

1. Request Header:

   • Allows you to add headers to outgoing requests sent to the origin server.

2. Add Header:

   • Adds custom headers to requests, enabling additional metadata or instructions to be included.

3. Hide Header:

   • Hides specified headers from being included in requests sent to the origin server.

4. Request Header Delete:

   • Removes specific headers from requests before they are sent to the origin server.

How to Configure Custom Headers

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section in the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to configure custom headers.

3. Click on the Headers tab.

4. Enable Custom Header Settings: Locate the Custom Header section and toggle the setting to On.

5. Add Header Actions:

   • Click the + button to add a new header configuration.

   • Choose one of the available actions:

     • Request Header

     • Add Header

     • Hide Header

     • Request Header Delete

   • Enter the key and value for the header based on the selected action.

6. Add Multiple Headers (Optional):

   • Click the + button again to add additional header configurations as needed.

7. Submit Your Configuration: Once all header actions are defined, click the Submit button to save and apply your changes.

The Origin Host Header feature in the Medianova Cloud Panel allows you to specify a custom host domain to be used in the Host header for origin server requests. This can be useful for scenarios where the origin server expects a specific domain for routing or validation purposes.

Key Features

• Custom Host Domain: Specify a custom domain to be sent in the Host header for all requests to the origin server.

• Flexible Configuration: Supports any valid domain format without including http:// or https://.

• Enhanced Compatibility: Useful for multi-tenant or shared hosting environments that rely on domain-specific routing.

How to Configure Origin Host Header

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section from the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to configure the Origin Host Header.

3. Click on the Headers tab.

4. Enable the Origin Host Header: Locate the Origin Host Header setting and toggle it to On.

5. Enter the Host Domain:

   • In the input field, specify the domain to be used in the Host header (e.g., subdomain.example.com).

   • Ensure the domain is entered without http:// or https://.

6. Submit Your Configuration: Click the Submit button to save and apply your changes.

By configuring the Origin Host Header, you can ensure compatibility with origin servers that require specific domain headers, improving routing accuracy and server behavior.

The HTTP Strict Transport Security (HSTS) Protection feature in the Medianova Cloud Panel enforces secure connections by ensuring that all HTTP requests are redirected to HTTPS. This helps protect against protocol downgrade attacks and cookie hijacking.

Key Features:

• Max-Age Setting: Define the duration (in seconds) that browsers should remember to only use HTTPS for your domain.

• Include Subdomains: Optionally enforce HSTS for all subdomains of your domain.

• Preload Option: Enable inclusion in the HSTS preload list, ensuring strict HTTPS enforcement even before the first visit.

How to Configure HSTS Protection

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section in the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to enable HSTS protection.

3. Click on the Headers tab.

4. Enable HSTS Protection: Locate the HSTS Protection setting and toggle it to On.

5. Configure HSTS Settings:

   • Max Age (Seconds): Enter the duration in seconds for which browsers should enforce HTTPS (e.g., 31536000 for one year).

   • Include Subdomains: Set to True to apply HSTS to all subdomains, or False to limit it to the main domain.

   • Preload: Set to True to include the domain in the HSTS preload list, or False to exclude it.

6. Submit Your Configuration: Click the Submit button to save and apply your HSTS settings.

By enabling HSTS Protection, you enhance your website's security, ensuring HTTPS is strictly enforced for all connections.

The X-Frame Options feature in the Medianova Cloud Panel enhances your website's security by preventing unauthorized embedding of your content on other websites. This is achieved by configuring the X-Frame-Options HTTP header, which protects against clickjacking attacks and unauthorized framing.

Key Features

• Control Content Embedding: Prevent your content from being embedded on unauthorized domains.

• Domain-Specific Configuration: Specify which domains are allowed to embed your content.

• Multiple Domain Support: Add multiple domains as exceptions if needed.

How to Configure X-Frame Options

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section from the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to configure the X-Frame Options.

3. Enable X-Frame Options: Locate the X-Frame Options setting and toggle it to On.

4. Add Allowed Domains:

   • In the input field, enter the domain you want to allow for embedding (e.g., example.com).

   • Click the + button to add additional domains if required.

5. Submit Your Configuration: Click the Submit button to save and apply your changes.

By enabling X-Frame Options, you can safeguard your content from unauthorized usage, ensuring better security and control over how your resources are utilized.

The efficiency of a Content Delivery Network lies not just in content delivery but also in its ability to swiftly purge outdated or updated content. Purge operation is the process of deleting your content on cache servers in Medianova CDN architecture. If you have made changes to your existing content and you want to make it active immediately without waiting for the cache to expire, you can use the purge operation.

The steps you need to follow are as follows.

2. You can reach the Purge setting by clicking on the CDN Resource you would like to edit by following the CDN → CDN Resources path on the left side of the panel and navigating to the Purge tab.

3. After entering the path information of the contents you want to purge in the box, you can perform the purge operation by pressing the Purge Files button.‏‏‏‏‏‏‏

Wildcard Purge

Wildcard Purge is supported. You can use * to specify the path and pattern.

Example: /example/images/im* /example/images/*

• Please note that purging /example/images/* will also result in the removal of all subdirectories recursively within example/images, such as example/images/subdirectory/.

The efficiency of a Content Delivery Network lies not just in content delivery but also in its ability to swiftly purge outdated or updated content. Purge operation is the process of deleting your content on cache servers in Medianova CDN architecture. If you have made changes to your existing content and you want to make it active immediately without waiting for the cache to expire, you can use the purge operation.

The steps you need to follow are as follows.

2. You can reach the Purge setting by clicking on the CDN Resource you would like to edit by following the CDN → CDN Resources path on the left side of the panel and navigating to the Purge tab.

3. After entering the path information of the contents you want to purge in the box, you can perform the purge operation by pressing the Purge Files button.‏‏‏‏‏‏‏

Wildcard Purge

Wildcard Purge is supported. You can use * to specify the path and pattern.

Example: /example/images/im* /example/images/*

• Please note that purging /example/images/* will also result in the removal of all subdirectories recursively within example/images, such as example/images/subdirectory/.

X-XSS Protection

The X-XSS Protection feature in the Medianova Cloud Panel helps protect your website from Cross-Site Scripting (XSS) attacks by enabling the XSS filter built into modern web browsers. When activated, this feature prevents malicious scripts from executing in the browser, enhancing your website's security.

Key Features

• Built-in Browser Protection: Leverages the XSS filter already present in most modern web browsers.

• Simple On/Off Toggle: Quickly enable or disable the protection as needed.

How to Configure X-XSS Protection

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section from the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to enable X-XSS Protection.

3. Enable X-XSS Protection: Locate the X-XSS Protection setting and toggle it to On to activate the feature.

4. Submit Your Configuration: Click the Submit button to save and apply the changes.

Notes:

• When On, the browser's XSS filter is activated, blocking or sanitizing malicious scripts.

• When Off, the browser does not filter potential XSS attacks, leaving your website more vulnerable.

By enabling X-XSS Protection, you enhance your website’s resilience against XSS vulnerabilities, ensuring a safer browsing experience for your users.

Free SSL certificates offer a cost-effective way to secure your services without compromising on security standards. In the Medianova Cloud Panel, you can easily enable and manage free SSL certificates through the intuitive SSL Management interface. This guide walks you through the steps to activate and utilize free SSL certificates for your organization.

2. Click on the “CDN → SSL Management” option on the left menu of the panel.

3. To add a new SSL certificate to your organization, click on the “Add New SSL” button on the SSL Management page.

4. Select the Free SSL button.

1. Fill in the SSL Name field. Select the Wildcard option as optional. Select the relevant domain.

2. Click the Add SSL button.

3. In the next step, follow the instructions for Let's Encrypt domain verification.

4. Click the Confirm button.

5. The SSL installation process has been completed successfully.

The X-Content-Type-Options feature in the Medianova Cloud Panel helps protect your website from MIME sniffing vulnerabilities by ensuring that browsers adhere strictly to the content type specified by the origin server. This prevents browsers from interpreting content types incorrectly, reducing the risk of attacks like cross-site scripting (XSS) or content injection.

Key Features

• Prevent MIME Sniffing: Disables the MIME sniffing functionality in browsers like Internet Explorer and Chrome.

• Strict Content Type Enforcement: Ensures that the browser uses the MIME type sent by the origin server, rather than attempting to infer the content type.

• Simple On/Off Toggle: Quickly enable or disable the feature with a toggle.

How to Configure X-Content-Type Options

1. Log in to the Cloud Panel: Access the Medianova Cloud Panel and navigate to the CDN Resources section from the left-hand menu.

2. Select the Relevant Resource: Choose the resource where you want to enable X-Content-Type Options.

3. Enable X-Content-Type Options: Locate the X-Content-Type Options setting and toggle it to On to activate the feature.

4. Submit Your Configuration: Click the Submit button to save and apply your changes.

Notes:

• When On, browsers are instructed to respect the content type specified by the server, preventing them from attempting to detect the MIME type on their own.

• When Off, the browser may try to infer the MIME type, which could potentially lead to vulnerabilities if the content is misinterpreted.

Enabling X-Content-Type Options is an important security measure that helps protect your site from content-type-based vulnerabilities and ensures that browsers handle content as intended.

The Prefetch in the Medianova Cloud Panel allows you to proactively load and cache specific content in the CDN data centers before it is requested by end users. This is especially beneficial for large files or frequently accessed resources, as it ensures that these files are readily available at the edge servers, significantly reducing load times and enhancing the user experience.

What is Prefetch?

Prefetch refers to the process of downloading or caching content in advance, before it is actually needed by the end user. This strategy is used to anticipate the content that users may request and store it closer to them at the CDN's edge servers. By prefetching content, you reduce the time it takes to retrieve data from the origin server and serve it to the user, thus speeding up the delivery of content.

When content is pre-cached at CDN edge locations, the CDN can serve it directly to the user, bypassing the need to make requests to the origin server for every user. This is particularly useful for resources that are large in size or are accessed frequently, such as images, videos, or large datasets.

Key Features of the Prefetch

• Pre-cache Large Files: The tool allows you to pre-populate large files in the CDN edge locations, ensuring they are ready for delivery when requested by users.

• Reduced Latency: By having content preloaded in edge locations, it can be served much faster to users, reducing latency and improving load times.

• Efficient HTTP Pull Content: The Prefetch Tool is particularly effective for HTTP pull content, where the server pulls the content when a request is made. Prefetching ensures that these files are already in the CDN, minimizing the time it takes to retrieve and serve them.

• Improved User Experience: By reducing the time it takes to fetch large or popular content, you improve the overall user experience, leading to faster website load times and more efficient content delivery.

How to Use the Prefetch

1. Log in to the Cloud Panel: Begin by accessing the Medianova Cloud Panel. From the left-hand menu, navigate to the CDN Resources section.

2. Select the Resource: Choose the relevant resource where you want to enable the Prefetch. This can be a specific file or set of files that you wish to pre-cache.

3. Enter the File Path: Specify the path of the file you want to prefetch. This can be the full URL or a relative file path from your server. For example, you might enter the path to a large video file, a high-traffic image, or any other resource you wish to cache in advance.

4. Click the Prefetch Button: After entering the file path, click the Prefetch button. This will trigger the caching process, where the CDN will begin downloading and storing the content at the edge servers.

5. Monitor the Process: Once the prefetch process begins, the specified content will be cached at CDN edge locations, ensuring that it is ready to be served when a user requests it. You can monitor the status of the prefetching process through the Cloud Panel interface.

Why Use the Prefetch?

Prefetching is an effective method for optimizing the delivery of content that is either large or frequently accessed. Common use cases for the Prefetch include:

• Media Files: Prefetching large video, audio, or image files ensures they load instantly for users, improving performance and reducing buffering times.

• Popular Resources: Files or assets that are regularly accessed by users can be pre-cached to ensure they are readily available, avoiding delays caused by waiting for them to be pulled from the origin server.

• High-Traffic Pages: For websites or applications with high traffic, prefetching important files ensures that content is always available at the edge, preventing slowdowns or delays during peak usage times.

By leveraging the Prefetch, you can significantly improve the speed and efficiency of your content delivery, ensuring a better overall experience for your users.

Best Practices for Prefetching

• Prioritize High-Impact Content: Focus on prefetching content that has a significant impact on user experience, such as large media files or popular resources.

• Monitor Cache Hit Rate: Track how often pre-cached content is served from the CDN. If certain files are not being requested as often, consider removing them from the prefetch queue to optimize your cache usage.

• Use Prefetching for Large Files: Prefetching is especially useful for large files that take longer to load, as it allows these files to be available on the edge servers before a user requests them.

By using the Prefetch, you are proactively optimizing your content delivery and ensuring that your users receive a fast and seamless experience, especially when dealing with large files or resources that are accessed frequently.

Phalcon is a high-performance PHP framework that is open source and available to developers with MVC logic. Unlike many PHP skeletons on the market, it is written as an extension to PHP with C.

In this document, we have described alternative ways to integrate between Phalcon and Medianova CDN.

1. First, create the Zone for account.

2. We recommend the first option to make the integration; define setStaticBaseUri.

<?php

$url = new Phalcon\Mvc\Url();

// Dynamic URIs remain on your origin server
$url->setBaseUri('/');

// Static resources go through MedianovaCDN
$url->setStaticBaseUri('http://your-origin-url.com/');

1. As an alternative to this path, use the collections and add a URL-prefix for CDN URL

<?php

$css = $this->assets->collection('header');
$scripts = $this->assets->collection('footer');

if ($config->environment == 'development') {
    $css->setPrefix('/');
    $scripts->setPrefix('/');
} else {
    $cdnURL = 'http://your-cdn-url.com/';
    $css->setPrefix($cdnURL);
    $scripts->setPrefix($cdnURL);
}

$css->addCss('css/bootstrap.min.css')
        ->addCss('js/custom.css');

$scripts->addJs('js/jquery.js')
        ->addJs('js/bootstrap.min.js');

1. The last alternative offered

...
$cdnURL = 'http://your-cdn-url.com/';
$this->assets
     ->addCss($cdnURL.'css/custom.css', false);
...

1. Check your HTML source code learn whether (or not) load your assets from Medianova CDN.

WordPress, one of the world’s most common content management systems (CMS); Open source structure, easy installation and user-generated theme and plug-in support for each topic has a use.

With WordPress, it is possible to create a blog, business site, portfolio, an online store or anything of your dreams. Many users around the world may want to access content on a website created with WordPress. But that’s it doesn’t possible all the time!

You need to make a good CDN selection for a fast-loading WordPress site. With Medianova CDN; static content on WordPress pages will no longer be delivered from the source server, but always from the nearest Medianova CDN server.

You can easily change the static content URL with CDN URL using the “Medianova CDN” plugin. You follow the following steps make the Medianova CDN WordPress integration.

2. Enter the WordPress admin panel.

3. Open a new plugin page by clicking go to Plugins → Add New in the WordPress menu.

1. Search the search engine for the keyword “Medianova”.

1. Download the plugin and activate it first if it is not active.

2. If the plugin is active, go to the Plugin settings page by clicking Settings → CDN Medianova.

1. Enter the CDN URLs, folders to include, and file extension to exclude and click “Save Changes”.

Medianova as Turkey’s largest e-commerce companies to offer CDN services to ensure high performance and speed. If you have an e-commerce site that works on Magento and you want to provide faster service to your customers, you should provide integration between Medianova’s CDN and Magento. Here are the steps you need to follow.

Magento – Medianova Integration

1. First, Create your Zone for account

2. Enter the Magento admin panel, Click the Stores> Configuration section from the left menu

3. Then select General> Web using the sub-menu

4. Open the Base URLs section

5. For this Static View Files, enter /static/ at the end of the Zone URL in the Base URL

6. Similarly, in the Base URL field reserved for User Media Files, add /media/ at the end of the Zone URL.

1. Save the configuration

2. Go to System> Cache Management in the menu on the left side

3. Update all outdated caches and click the Flush Magento Cache button.

That’s all you need to follow for Magento 2 CDN integration!

Magento Medianova Integration

1. First, Create your Zone for account.

2. Enter the Magento admin panel, Click the System> Configuration section from the top menü.

1. Go to General> Web section using the left menu.

2. Click the “Unsecure” section and enter the information to coming screen.

1. If you want to use HTTPS protocol, you need to select “Secure” option and enter the information on the screen.

1. Save all settings and complete Magento CDN integration

CakePHP is an open-source framework, such as Zend, Laravel, and Symfony, developed with MVC (Model-View-Controller) logic and on PHP.

We have explained the CDN integration steps that support the CakePHP 2.4 version and higher versions for you.

1. First, create the Zone for account.

2. Add the base URL variables in the ./Config/bootstrap.php config file for define Medianova CDN in bootstrap.

CODE

Copy

1. Use the HTML helper for image HtmlHelper::image.

<?php echo $this->Html->image('your-logo.png', array('alt' => 'Your Logo')); ?>

Will Output:

CODE

1. Use the HTML helper for CSS HtmlHelper::css

Will Output:

1. Use the HTML helper for JavaScript HtmlHelper::script

CODE

1. Check the HTML source code to find out your assets whether (or not) loading from Medianova CDN.

This feature allows you to define rules on files or file formats for content they hold under our CDN structure.

To use this feature;

2. You can reach the Page Rule settings screen by clicking on the CDN Resource you would like to edit by following the CDN -> CDN Resources path on the left side of the panel and navigating to Page Rules tab.

3. You can create a page rule by clicking on the Create Page Rule button, entering the path information and selecting the file extension and operation type.

• Path: Enter the path that you would like to define the page rules for. Only one path at a time can be entered.

  • / * would mean that the settings apply to all files and folders.

  • / cdn / would mean that the settings apply to files and folders under the CDN folder.

• File Extension: The extensions for which the rules will apply are specified without a dot. Multiple extensions are written with a comma.

  • jpg

  • jpg, png

• Valid Referrers: Only requests from the specified websites are allowed, others are rejected. Multiple values are written with comma.

  • .com

  • .com, *.medianova.com

• Browser Cache: It defines the amount of cache time for the browser (Google Chrome, Firefox).

• Cache Time: It defines the cache time for the content on CDN servers.

• Ip Restriction: It defines for which IPs the content will be available. The content can be accessed by the IPs that are given. If left blank, it will be available for all IPs. You should use a comma for entering multiple IPs.

  • 168.2.1

  • 168.2.1, 192.168.2.2

  • 111.28.0 / 24 (can be defined as IP block.)

• Security Headers: Security headers can be enabled to prevent hostile attacks and penetrations.

  • X-XSS Protection: To protect your website from XSS (Cross-Site-Scripting) attacks, header information can be added to the response header on the server side.

  • HTTP Strict Transport Security: HSTS converts the HTTP request made by a user through the web browser to automatic HTTPS. It provides a more secure connection between servers.

  • X-Frame: Clickjacking technique, which is one of the hidden attacks used to click on the Internet users without being aware of them, is related to the X-Frame Options Header.

  • X-Content Type: Supported by Chrome and IE browsers, X-Content-Type-Options is the Security Header that analyzes the file type of the content by doing MIME Type Sniffing on the webserver.

• Custom Headers: It contains three different values. These are:

  • Request Header Add: It contains header information sent to the origin server.

    • XCDN medianova “Can be written as an example.”

  • Add Response Header: It contains header information to be displayed on the browser. Users can view these headers by doing a resource review.

    • XCDN medianova “Can be written as an example.”

  • Hide (Response Header Concealment): Headers to hide

    • Expires “Can be written as an example.”

• Afterwards, you can view, edit and delete the existing custom paths from the settings button on the right.

When it comes to content delivery, there are two primary categories: static and dynamic. Static content remains the same for every user, delivered without server processing. It's fast and easy on server resources. On the other hand, dynamic content is generated for each request, involving database queries and extensive code execution. Delivering dynamic content can be resource-intensive.

Our intelligent microcaching system allows to cache dynamic web content or API responses for even a second, reducing the load on origin servers, resulting in faster page load times and reduced bandwidth costs.

How does Dynamic Content Caching work?

Website Caching

Many websites unnecessarily regenerate content for every page view. Full Page Caching (FPC) addresses this by caching the entire HTML document of a webpage.

Website caching dramatically reduces load times, and helps to cut server load, significantly enhancing the user experience.

API Caching

Web applications often make API calls to retrieve information for users. Examples include pricing data, form auto-completion, and product catalog searches. Caching these API calls reduces server load and accelerates website responsiveness.

Important Configurations

Set a brief caching period to ensure the cache remains relatively up-to-date. While effective for busy sites, lower traffic sites may experience lower cache hit rates.

Cache Time: This parameter dictates how long the CDN retains cached content before refreshing it from the origin server. The optimal cache time depends on the nature of your content, update frequency, and the traffic patterns your website experiences.

Page Rules: Not all pages are created equal, and some dynamic or personalized content may not benefit from caching. Configuring which pages to exclude from the cache is very important. Here are some examples to exclude.

• Checkout Pages:

  • Exclude pages in the checkout process to ensure real-time, up-to-date transaction information.

• Customer/Admin Areas:

  • Keep personalized customer or administrative areas dynamic, avoiding potential issues with serving outdated content.

• Highly Dynamic Content:

  • Identify pages with content that changes frequently or is highly personalized; exclude them to maintain accuracy.

1. The IP address of the CDN URL shared with you by the Medianova Technical Sales team or created via a Free trial can be found as follows.

• The CDN URL is pinged by opening the Command Prompt. (CDN URL = <zone_name>.mncdn.com)

Example: ping <zone_name>.mncdn.com

1. The IP address retrieved above is written to the “host” file of your computer.

• Open the Run tab by pressing the Windows key + R.

• Type system32 in the search bar and click ok.

• On the screen that opens, navigate to the drivers folder and open it.

• Navigate to the etc folder in the “drivers” folder and open it.

• Right-click on your “host” file and choose open with. Edit it with one of the applications such as Notepad or Notepad++.

• Add the IP address you obtained in the first step and the website you want to reach using this IP address and save the file as shown below.

The Advanced Origin Settings feature provides a flexible and efficient way to configure content routing for dynamic resources. It allows you to define specific rules for routing requests to your origin server based on criteria such as URIs, protocols, domains, ports, and more. This functionality is particularly valuable for delivering dynamic content where precision and adaptability are crucial.

Key Benefits

• Optimized Routing for Dynamic Content: Ensures requests for frequently changing or personalized content are routed efficiently to the origin server.

• Flexible Matching Rules: Define custom routing rules based on URI patterns, protocols, or domain structures to align with complex backend logic.

• Enhanced Performance: Reduces latency and improves response times for real-time content by fine-tuning origin configuration.

How to Configure Advanced Origin Settings

1. Click on the CDN Resources section in the left-hand menu of the Cloud panel.

2. Select the relevant resource.

3. Click on the Origin Settings tab.

4. Navigate to the Advanced Origin Settings section in the Medianova Cloud Panel.

1. Click the Add button to open the configuration popup.

2. Fill in the following fields:

   • URI Match Mode: Select the matching mode for URIs (e.g., exact match, prefix, or regex).

   • URI Match Rule: Define the URI pattern based on the selected mode.

   • Protocols: Choose between HTTP, HTTPS, or Same as Request to determine how the traffic should be routed.

   • Domain or IP: Enter the domain or IP address of the origin server.

   • HTTP Port: Specify the HTTP port to use for connections.

   • HTTPS Port: Specify the HTTPS port to use for secure connections.

   • Host Header: Provide a custom host header if required for the origin server.

   • Priority: Assign a priority level to this rule to determine its precedence in case of multiple matching configurations.

3. Click the Add button.

4. Click the Submit button.

1. Click on the CDN Resource menu, select the CDN Resource you created and move to the Caching menu.

1. First you need to configure the Cache Settings at the bottom of the page. Cache Type field provides two options.

   1. If you would like to use the cache time defined on the origin with the cache-control header, you can select “Origin”. If you would like to set custom cache time, you can select “Edge”.

   2. When you select Edge, you should set the cache time, which indicates the maximum age of your cached content. Then you should also specify if you would like to cache dynamic content such as your HTML files and click the Save Changes button.

1. Next, you need to check your Query String Caching settings. You can leave the Query String setting disabled, if you would like to cache your files by ignoring query strings; or you can enable it to treat each query string as a cacheable item.

1. If “Cache Dynamic Pages” option under Cache Settings has been enabled at Step 4.1, that means all HTML files served by your origin and all resources (CSS, images, JavaScript) found in HTML files, will be cached and served through Medianova CDN.

However, it is recommended to exclude some of the HTML files which contain private information (such as account details, credit card information on check out page etc.). Below are two options to disallow caching, either by defining paths or by using cookies.

a. Disallow Caching by Defining Paths: Go to the Page Rules menu and enter custom paths to bypass caching under “Disallow Cache Rule” setting.

b. Disallow Caching by Using Cookies: Go to the Caching menu and enter Cookie Key & Cookie Value to bypass caching under “Disallow Cookie Base Cache” setting.

1. Go to the SSL menu and upload your SSL certificate.

1. You can test your Aksela account before redirecting your Website URL to your CDN URL, and serving traffic through our platform.

2. To start testing, first you need to find the IP address of the CDN URL. In order to do that, you can ping your CDN URL on Command prompt.

Example: ping cdnresource_name.mncdn.com

b. Then, you need to add this IP address to your hosts file.

- Open the Run tab by pressing Windows key + R.

- Type system32 in the search bar and click ok.

- On the screen, go to the “drivers” folder and then to the “etc” folder.

- Under the “etc” folder, you can right-click on your “hosts” file and select open and edit with application such as Notepad or Notepad++.

- Please add the IP address you obtained in the first step and the website you want to reach using this IP address to the file and save it.

c. Clear your browser cache. Make a request to the page by typing yourdomain.com in the address bar. On the page that opens, right-click on an empty area and select “inspect”. Go to the “Network” tab and find your Website URL within the list of requests. Click on it and and display the information in the “Headers -> Response Headers” area. Seeing “MNCDN” next to the “Server” field shows that the .html file is served from Medianova.

1. After completing the test successfully, login to your DNS hosting provider’s client panel and add a CNAME record for redirecting your Site URL to the CDN URL you have created.

   yourdomain.com IN CNAME cdnresource_name.mncdn.com

2. Your traffic is now served through Medianova Aksela.

Aksela is a micro-caching platform developed by Medianova. Micro caching ensures that your content can be cached even for seconds. It serves static & dynamic content and API requests on your website through edge servers closest to end users.

By laying between the origin server and the end user, Aksela both increases performance and provides an additional layer of security. In addition to the security measures provided by Aksela, WAF (Web Application Firewall) can be provided as an additional security service.

1. Click on “CDN → Create CDN Resource” option from the menu on the left side of the panel.

1. In the next screen, Dynamic CDN Resource is selected from the “Start building your CDN”

1. Fill in the requested information for Dynamic CDN Resource.

Static CDN is primarily used for delivering fixed content, such as images, CSS files, and JavaScript files. These resources are typically unchanged, which allows for faster delivery through a CDN. The Static CDN Analytics section provides key metrics that help monitor, analyze, and optimize the performance of static content delivery. These metrics focus on the caching effectiveness, the amount of traffic being served from the cache versus the origin server, and the overall bandwidth usage.

Traffic

• Total Traffic: This chart displays the total amount of traffic delivered during a selected time range. Users can view the traffic over a custom time range or compare it with the previous time range to understand the trends and fluctuations in traffic. A significant increase in traffic indicates that the content is being accessed more frequently, which can be beneficial for scaling infrastructure and improving cache efficiency.

• Traffic in Time: This chart provides insights into traffic variations over time. By analyzing traffic patterns, you can identify spikes in demand, possibly caused by promotions, seasonal events, or viral content. It also helps determine when content delivery peaks, assisting in optimizing server performance during high-traffic periods.

• Cached vs Non-Cached: This chart compares traffic served from the cache versus traffic retrieved from the origin server. High cache traffic indicates that most of the data is being served efficiently from the CDN, reducing load on the origin server and speeding up delivery to end-users. A low cache hit ratio might indicate a need for better cache configuration or optimization.

• Cached Data: This chart shows the breakdown of cached data into hits, updating, and stale categories:

  • Hits: Content successfully retrieved from the cache.

  • Updating: Content that is currently being updated in the cache.

  • Stale: Content served from the cache that is outdated because the origin server did not respond in time. These metrics are crucial for understanding cache freshness and the efficiency of the content delivery process.

• Non-Cached Data: This chart shows the amount of data retrieved from the origin server, broken down into miss and expired categories:

  • Miss: Content that was not found in the cache and had to be fetched from the origin server.

  • Expired: Cached content that has expired and needs to be fetched again from the origin server. A higher proportion of non-cached data suggests that caching is not being utilized effectively, which could lead to higher latency and bandwidth usage.

Bandwidth

• Bandwidth: This chart shows the total bandwidth used for delivering static content. High bandwidth usage might indicate large file sizes or a high volume of requests, which can be optimized through compression, better cache utilization, or content delivery strategies.

• Cached vs Non-Cached: This chart compares the bandwidth used for cached versus non-cached data. Ideally, cached data should consume most of the bandwidth, as it reduces the need for repetitive fetching from the origin server, resulting in faster load times and reduced network strain.

Requests

• Total Requests: This chart displays the total number of requests made for static content. A high number of requests indicates active content consumption, which is useful for monitoring content popularity and server load.

• Hits vs Misses: This chart compares the number of requests that resulted in a cache hit versus a cache miss. A higher hit ratio is ideal, as it indicates that the CDN is effectively serving content from the cache, reducing the need to contact the origin server.

• Request Hits: This chart shows detailed information on hits, broken down into hit, updating, stale, and revalidated categories:

  • Updating: The content is in the process of being updated.

  • Stale: The content is outdated and served while awaiting a response from the origin server.

  • Revalidated: The cached content has been successfully revalidated with the origin server and is now fresh. These metrics provide insights into the cache's efficiency and freshness.

• Request Misses: This chart shows detailed information on misses, broken down into miss and expired categories:

  • Miss: The content was not found in the cache and was fetched from the origin server.

  • Expired: The cached content expired and had to be retrieved from the origin server again. Analyzing this data helps in understanding the reasons for cache misses and optimizing cache configurations.

Status Codes

• Total Requests: This chart displays the total number of requests, helping you track overall activity and performance.

• Status Code Structure: This chart compares the distribution of different HTTP status codes:

  • 2xx: Successful responses (e.g., 200 OK).

  • 3xx: Redirects (e.g., 301, 302).

  • 4xx: Client errors (e.g., 404, 403).

  • 5xx: Server errors (e.g., 500, 502). Monitoring these status codes helps identify potential issues in content delivery and client-side or server-side errors.

• Successful Responses (2xx): This chart shows the distribution of successful responses, particularly focusing on the 200 OK code and other 2xx codes. High 2xx responses indicate that the CDN is successfully delivering content.

• Redirects (3xx): This chart displays the distribution of redirect codes (301, 302, etc.). Redirects can indicate changes in content location, which should be minimized for optimal performance.

• Client Errors (4xx): This chart shows errors on the client side, such as 403 (Forbidden), 404 (Not Found), and 429 (Too Many Requests). A high number of client errors suggests that users are requesting unavailable content or facing access issues.

• Server Errors (5xx): This chart shows server-side errors, such as 500 (Internal Server Error), 502 (Bad Gateway), and 504 (Gateway Timeout). These errors indicate issues on the origin server and require attention to ensure smooth content delivery.

Error Logs

Error logs provide a detailed record of requests that resulted in errors. By selecting a specific error code, users can view logs that include the request path, method, protocol, and hit status. The logs are invaluable for identifying patterns and resolving recurring issues in content delivery.

The Rewrite Origin URLs feature enables precise control over how dynamic requests are routed to the origin server. By defining flexible rewrite rules, you can seamlessly map public-facing URLs to complex backend structures, ensuring efficient content delivery for frequently changing or user-specific resources.

Key Features

• Match Mode Options: Define dynamic matching criteria to identify URL patterns that require rewriting. Supports regular expressions and parameter-based matching for complex routing scenarios.

• Dynamic Origin URI: Specify dynamic or user-specific URIs that trigger the rewrite rules, ensuring accurate routing for content generated in real time.

• Target URI: Set the destination URIs to which requests will be rewritten. Supports placeholders and query string management for personalized and API-driven content.

• Priority-Based Execution: Assign priorities to rewrite rules to ensure correct execution order, especially when multiple rules overlap.

Key Benefits

• Optimized Content Routing: Ensures real-time requests are directed to the correct origin endpoints, even when public-facing URLs differ from backend paths.

• Improved Backend Integration: Allows seamless integration with origin servers that use dynamic or customized URL structures.

• Enhanced Flexibility: Supports complex URL rewrites using regular expressions and query string management for APIs, dynamic resources, or personalized content.

• Reduced Latency: Enables direct mapping of public URLs to backend resources, reducing processing time and improving overall response speed.

• Scalable Personalization: Dynamically adapts routing for user-specific requests, ensuring accurate delivery of tailored content without exposing backend complexities.