Wednesday 25 January 2012

Now, Using CDN-Power!

Using a CDN has been on my list for some time now, and I've finally gotten around to configuring one. I just changed the tracking snippet to use Amazon's CloudFront CDN, ensuring that the tracking snippet is edge-cached at over 25 locations world-wide, in North America, South America, Europe and Asia. This means that your users will get the least possible delay in loading Errorception's tracking code. Your users get blazing high performance by default! And boy, do we at Errorception love high performance. :)

This change is being rolled out all of Errorception's users, whether on the free trial or on any of the paid plans, at no extra cost.

Action required

Unfortunately, to use the CDN you will have to change your tracking snippet in your site. Log in, and go over to Settings > Tracking Snippet to get your new tracking snippet, and replace the old tracking snippet in your site with the new one. I know it's a chore — I apologize for the inconvenience. However, the benefits far outweigh the little trouble.

While the old tracking snippet will continue to work for some more time, I urge you to upgrade soon so that you can make the most of the CDN. At some point in the not-too-distant future, the old tracking snippet will not be supported anymore.


  1. Rakesh,

    noticed you link directly to the cloudfront url in your snippet (

    Major downside, you couldn't switch CDN's, nor is it a permanant URL given by Amazon (neither which you can re-claim if you deleted it).

    On the longrun it is much wiser to add a CNAME to your own DNS records like pointing to your CDN files.


    1. Yvo,

      You are absolutely right. However, Amazon doesn't allow CNAMEs over SSL at the moment. As a result, I could either use CNAMEd URLs over HTTP and the full Amazon URL over SSL, but that then brings me back to the same problem. You are right in that I'm taking a risk by using their domain, but there isn't a way around it at the moment. *sad face*