Integrating your website into the CDN will bring many advantages for your traffic and conversion rates. Most of the loading time of your website involves waiting for the files to download. If you use a CDN, these files will always be located on the server nearest to your visitor. Your visitor will experience very limited latency in the network, meaning the files will be loaded by the speed of light. Overall this gives the visitor a very fast experience, reducing the load time of your websites to just a few seconds.
EnterCDN gives your site a real competitive edge, by enhancing performance and consequently, your SEO. This will enable you to improve your search engine ranking.
Another feature of the EnterCDN is that it also works as a shield for your website by blocking external threats (abusive crawls, DDoS attacks).
CDN acts as a protection for your website. The CDN PoP network can absorb denial of service attacks, bots that crawl the site to overload the server, and loss of connection. Your website is protected by the network, reducing risks to your critical applications and thus improving QoS.
The number one reason for using a CDN is to improve your user's experience in terms of speed! Ensuring a consistent experience for all your users is important particularly to professionals with international websites, or those wishing to develop their business internationally, without deploying complex infrastructure or increasing operating costs, and looking to save on current hosting packages. A CDN adapts to any type of site; e-commerce, content sharing sites, news sites, blogs, etc.
HTTP Pull is probably the most frequently used CDN method/protocol. It's recommended for the delivery of small static content via CDN edge servers - content like images, css and pdf files. With HTTP Pull, content is cached on edge servers when a user requests that content.
The detailed workflow is as follows:
- A visitor requests content from a website.
- The CDN logic determines which edge server is best placed to deliver that content.
- If the content is not already cached on that edge server, the CDN pulls the content from the origin via HTTP port 80.
Site owners may set the cache expiry on the origin, or define it in the advanced settings of the relevant CDN Resource.
The Origin URL is basically the URL of your website, or your domain.
The “Origin” is the destination on which your static assets are hosted/located, and from which we will pull and cache your files.
If your web server ever goes down, your websites will never go offline. Our CDN will keep serving all static content that is directly requested. Your visitors will be told when a cache page is being served to them until your web server is backup again.
When you purge a CDN asset delete the cached version of the asset from all of edge servers on the CDN network. This is useful when you update content on your site and want to ensure that your visitors get the latest assets. For example, if you have updated an image, or have made changes to your CSS file. Frequent purging is not recommended, because it will take additional time for cache to re-build each time you flush it.
There is no charge. HTTP Pull use caching space which is dynamically allocated and we don’t charge you for usage of it. Only bandwidth is charged.
When you will be serving large files, over 10 Megabytes of size, such as video, audio, streaming media or dynamic content are not supported on our HTTP PULL.
No, unless the contents are publicly available, we cannot pull them.
The default TTL (time to live) is 24 hours from the time when the file is initially cached. The Expires header is the original cache-related HTTP header and tells the cache (typically a browser cache) how long to hang onto a piece of content. However, if the files are given an expiry header on the (Origin) server on which they are hosted, using .htaccess or httpd.conf for example, we will honor the expiry header.
To enable CDN on your website, simply change the CNAME IP address of your DNS for the one provided in the email order confirmation. Be sure to check that you have permission to change your DNS. You will be then able to set your TTL, force or block caches, manage the SSL certificates, etc.
There are two following solutions to prevent search engines accessing duplicate content:
If you want both sites to be live, accessible and independent you should use robots.txt to prevent indexing of the newer version of the content. The original indexed content should be visible to search engines and not blocked in robots.txt
If you are just moving the site to a new location and don't need the existing original site to be live then 301 redirect it to the new location (in .htaccess).