Mistakes when setting up CDN

Picture of Written by BlazingCDN

Written by BlazingCDN

December 26, 2022

When we speaking of websites, faster is always better. Don’t let the customers leave your website because of the page load time. The utilisation of a CDN is a very effective way to deliver your data faster, however, if you don’t set your CDN up correctly, you can’t fully exploit its potential. 

Setting the expiration time

You have the option to set up the cache expiry even without using the HTTP headers.

You can set this value generally for the whole CDN Resource in your dashboard. If you have a high miss ratio (a big part of your traffic is non-cached), it might be (in very specific cases) due to the incorrect setting of this value (data being cached for only a short period of time). However, if you’re sending max-age and expiry headers, then we will respect the value of these rather than the value you set in the dashboard – CDN zone Preferences.

Solution 1: Set a longer period for your cache expiry.

Solution 2: Check – Min requests to cache.

Website with "cookies"

Most pages today use cookies. However, you may unintentionally also send them with static files, you want to be delivered through the CDN. This may be a problem since most CDN providers don’t cache any files with set-cookies by default.

If you are setting cookies for all your files – be that for advertising or any other reason – you would see all traffic uncached.

Setting the cache-control headers

Most pages today use cookies. However, you may unintentionally also send them with static files, you want to be delivered through the CDN. This may be a problem since most CDN providers don’t cache any files with set-cookies by default.

If you are setting cookies for all your files – be that for advertising or any other reason – you would see all traffic uncached.