Once you use Content Delivery Network such as Amazon Cloudfront to speed up your blog, you will come across instances when you update static file, but your readers keep getting the stale file from CDN.
The only way would be to invalidate the file, which will signal CDN to pull fresh copy from the location.
But this necessitates you to log on to CDN server, locate the file, generate invalidation request, and wait for it to percolate to all the mirrors.
You enter Version String in the plugin admin page, and append the same string where you define CDN address in your caching plugins, such as WP Super Cache or W3 Total Cache.
This way, when your reader loads page, he is looking for different file, and your CDN server will query your server for it, where this plugin will intercept the query and serve the modified file from the location.
In to the fully Lite, CDN Buster also has Pro version with many more features..
Content Delivery Network is collection of distributed servers that mirror and serve you static contents to your readers much faster than your own server can.
Since your resources on CDN have different address, the browser loads the statc content and the dynamic content in parallel, enhancing the user experience..
Most CNDs are of Origin Pull kind, where CDN server pulls file from location whenever it's asked to serve file it doesn't have in its cache.
Thereafter, whenever the file is requested, the file is served from closest to the reader...
Read more
Related items:
