6 ms·
bottom line: always CNAME your asset domain.
by lxfontes 12y ago
bottom line: always CNAME your asset domain.
- mikejholly 12y agoTotally. We were able to side step the CDN in less than a minute. +1
- Nagyman 12y agoThat helps! I guess it assumes your origin servers have the capacity to serve the traffic. Or did you switch CDNs? Just curious as there are services like Cedexis (or TurboBytes; the author of the article) for load balancing CDNs
- publicprivacy 12y agoWhat exactly is an asset domain? The one you setup to point to the CDN?
- ceejayoz 12y agoYes. Instead of using pqowieurpqoiwer.cloudfront.net, you can point one of your own subdomains at it. Leaves you in control. The only complexity is SSL certificates - you either have to pay $600/month for a custom cert, or use SNI and ditch some older IEs.
- sbarre 12y ago$600 per month for what exactly? (honestly asking here)
- micro-ram 12y agoCould you add a global variable to your site code with the fqdn of your assets to point to the origin for times like this?
- Xorlev 12y agoThey do offer free SSL with SNI. But that's not viable for most people given the number of popular older browsers missing SNI support.
- kbuck 12y agoBrowsers that do support SNI include: IE7+ (unless running on Windows XP) Firefox 2.0 and later Opera 8.0 and later Chrome 6 and later (unless running on Windows XP) Safari 3.0 and later Android default browser on Android 3.0 and later (this is probably the biggest chunk of users) Windows Phone 7 So, realistically, you're looking at people who still use Windows XP (unless they're using Firefox) and people with really old Android phones that'll never receive a manufacturer firmware update.
- cbsmith 12y agoMeh. Adds an extra DNS lookup. Just have a short TTL and let people who ignore it suffer. ;-)
- deleted 12y ago[deleted]
- eknkc 12y agoAnd burn down your backend servers. Assuming you are not swithing to another CDN that fast.