CDN Best practice
Posted by Sinan Esen on 03 September 2015 11:57 AM
Overview. CDN's are an excellent way to serve static content to both nationally based and international site visitors.
They work by taking the static content (Images, CSS, flat HTML) and caching them to our expansive CDN network of servers. When a visitor accesses your site, say from Australia, the initial request is sent to the CDN, where it serves back the static content and polls your server for any updated or new content (such as a news feed). This has the major benefit from reducing page load times from international visitors as we have CDN POP's (Points of presence) in NZ, AU, UK and USA.
Our CDN also helps reduce costly international bandwidth charges when serving traffic to foreign visitors by caching the larger images directly, reducing the traffic used by your server.
The main consideration before deciding a CDN is right for your site is to check if your site is using an SSL certificate. We cannot preserve the integrity of the SSL over the CDN (due to it having a different IP address from your site). This can be mitigated by ensuring the secure area of your site is served on a subdomain e.g. securearea.yourdomain.co.nz as opposed to yourdomain.co.nz. This is the perferred method of using the CDN on a site with an SSL.
You could also serve your static contend from a subdomain (as is common on the internet) for instance, all your photos, icons and other images could be served from images.yourdomain.co.nz.
Image reference without CDN
Image reference with CDN