Supersonic CDN overview
Supersonic CDN will help accelerate your website performance and deliver content to visitors fast, no matter where they’re located in the world. This guide will help you understand how CDNs work and how Supersonic CDN works.
A CDN (content delivery network) is a group of servers that are distributed across the globe for the purpose of caching (storing) and delivering assets (content such as images and video, for example) to website visitors faster.
Supersonic CDN has a comprehensive interface that gives you control over how your content is cached. Not only will Supersonic CDN increase the performance of a website, it also comes with a whole host of other that will improve its security and speed. These include DDoS protection, SSL handling, Website Security and Monitoring, Website Configuration, Cache Managing, Load Balancing, and more.
Before we dive into all that, let’s learn more about how a CDN works.
How a CDN works
Each request made to a website (e.g. a user loading a web page) has to go to the origin server (basically, that's the server where your content is hosted on), gather the requested assets (content), and return them to the client (your user’s computer). If the geographical location of a server and a client are far apart — if they are located on different continents, for instance — this request can take a long time, making load time slow. That's why it's recommended to choose a data center which is located close to your target audience.
A CDN works to minimize the virtual distance between the website’s visitor and the website’s server. It does this by storing a cached version of its content in multiple geographic locations (edge servers). By doing this, content can be delivered to end-users more quickly and reliably.
With a CDN, your customers should be able to access your website within milliseconds, no matter where they’re located.
Below you can find a comparison between non-CDN network and a CDN network:
- Page load speed improvement: CDN provides the fast delivery of Internet content by caching information on multiple servers around the globe so that users that pick up data from the closest server to them.
- Simple setup: A well-established workflow allows you to set up and manage CDN simply. So you can get your content delivery up and running fast, and don’t get lost in screens of settings and switches.
- Control of caching: With high-capacity SSDs and advanced caching techniques, we provide industry-leading cache depth to make more content available for longer at the edge server.
- Flexible Customization: You have the freedom to customize your asset delivery, security measures, SEO, and mobile experience to your needs.
- Real-time analytics: Leverage detailed data points about content delivery and traffic, with advanced reporting capabilities and analytics.
Supersonic CDN Dashboard
The Supersonic CDN dashboard features the following options:
Let’s take a closer look at the available options.
The Overview tab contains quick-links for settings, analytics, popular features, and access to manage quick actions:
Cache: clears all the cache from the website
DNS Records: allows to to apply the correct DNS records for Supersonic CDN
In the CDN Settings tab, you can see the Origin Address (address of your server).
This lets Supersonic CDN pull directly from your server. We will use it to retrieve content from the origin server.
The record will be added automatically to the Supersonic CDN settings for EasyWP-based websites.
For the automatic configuration for CDN with EasyWP subscription, you should start the configuration flow from the EasyWP admin dashboard.
: Currently, Supersonic CDN can be used only with Namecheap-registered
domains and if you are using our EasyWP
hosting and the domain is pointed to Basic DNS
or Premium DNS
. Check this guide
if you want to setup a Supersonic CDN with EasyWP.
It is possible to add a Namecheap domain pointed to Basic DNS or Premium DNS to the CDN App, but the CDN itself will not work for this domain unless it is using EasyWP.
Cache purging means removing cached content from CDN. When the cache is purged, every new request pulls the latest version of the content from your hosting server and adds the latest version to CDN.
If you select Purge all then all the cached content of your website will be removed from CDN.
Custom purge allows you to choose the exact assets to be purged.
Lifetime sets the maximum length of time that the CDN will cache your content for before going back to the origin server to get a new content, or defer to the value passed by your origin server.
Query String Control determines how you want Supersonic CDN to treat URLs that have a query string.
- Origin Controlled: The CDN will honor the cache-control headers, meaning that it will cache information during the time set up by the origin server. The cache-control header is used to specify directives for caching mechanisms in requests and responses. If you select the origin controlled option selected, you make the CDN cache the information during the time the origin server set up.
- Specify CDN TTL: You will choose the length of time the CDN will cache your content if you select this option. The Static content (all files for a website that are stored on a server) will be cached (and will not expire). Dynamic Content (changeable content) will be cached based on the origin cache-control headers.
- Never Expire: Static Content will be cached and will not expire, and CDN will use this saved information each time when delivering content. For example, when you enable this option and specify the header name there, we will cache all versions of that file.
- Do Not Cache: Static and Dynamic resources will not be cached, and a request will be sent to the origin server for each request. There are several reasons why you might do this. For example, someone could be using two sites working together and one could be dynamic, so one can decide not to use cache. Someone may want to hide the website behind CDN and use it as a proxy-pass, or cache just one type of file and define this by edge rules, etc.
A query string is a part of a URL that contains some parameters.They are extensions of the URL that are used to help define specific content or actions based on the data being passed.
Here is an example of a query string (everything after ? is a query string):
Setting a query string will allow you to cache separate versions of an asset based on a unique string. The query string allows you to control the caching of different versions of the same asset, to make sure requests get the correct version.
This is useful if you have URLs in your site with query strings — that is, if you have several versions of the same file.
URLs that contain string parameters will be controlled from your origin server.
- Ignore query strings: We will not cache every version of query strings for the entire website.
- Cache All Query Strings: This will cache all versions of each query string for the entire website.
- Custom: You can specify a URL or certain URLs paths by separating them with "," to cache query strings for.
With the help of the Cache exception option, you can choose a URL that won’t be cached — for example, if you want to cache only static content.
Gzip Compression allows you to reduce the file size of your content, which will improve delivery speed. It is possible to choose among the 6 levels of compression. The higher the level - the higher the compression.
Client Browser Policy
This part allows you to set up Browser Cache TTL (length of time that client browsers take to locally cache your content.), enable/disable CORS Header Support and HTTP/2 Support.
CORS (Cross-origin resource sharing) Header Support is a mechanism that uses additional HTTP headers to tell a browser to let a web application running at one origin (domain) have permission to access selected resources from a server at a different origin. That ensures the font files won’t be blocked on the browsers.
HTTP/2 is the revision of the HTTP network protocol. HTTP/2 makes applications faster, simpler, and more robust.
CDN service enabled for the website requires an SSL certificate issued for the website name to be installed for both EasyWP and CDN. You can use the same certificate files.
Feel free to check this guide
to learn how to add an SSL certificate to your EasyWP website.
The steps on how to install the SSL on CDN are described in this article
The Supersonic CDN Firewall option helps you to set up the level of the DDoS Configuration for your domain.
Firewall increases performance, security, and global distribution. It performs analysis to block malicious traffic from reaching your origin server.
- Domain threshold. This mechanism has a minimum DDoS threshold of 1,500 requests per 10 seconds and a maximum threshold of 100,000 requests per 10 seconds. If the customizable threshold value is met AND if the current number of requests is at least 2X the previous 10-second window then the DDoS mode will be activated.
This mechanism is responsible for identifying DDoS attacks that their traffic pattern consists of a slow rise in traffic over a period of time.
- Burst Threshold. This mechanism has a minimum DDoS threshold of 1,000 requests per 2 seconds and a maximum threshold of 80,000 requests per 2 seconds. If the customizable threshold value is met AND the number of requests is at least 5X the last 2-second interval, then the DDoS mode will be activated.
This mechanism is responsible for identifying sudden bursts in traffic.
- Sub Second Threshold. This mechanism has a minimum DDoS threshold of 50 requests per 100 milliseconds and a maximum threshold of 20,000 requests per 100 milliseconds. When the customizable threshold is met, the DDoS mode will activate on the WAF server that the traffic went through - compared to the other mechanisms that will activate DDoS mode for the entire WAF Cluster.
This mechanism is responsible for protecting against attacks that start with a burst and provides an extra layer of protection before the first 2 mechanisms will kick in.