Once you use a Content Delivery Network (CDN) such as Amazon Cloudfront to speed up your blog, you will come across instances when you update a static file (a style or image file, for instance), but your readers keep getting
一旦您使用诸如Amazon Cloudfront之类的Content Delivery Network（CDN）来加快博客速度，更新静态文件（例如样式或图像文件）时就会遇到实例，但是您的读者不断
the stale file from the CDN.
CDN中的陈旧文件。
No amount of cache clearing on your blog server is going to help refresh the cached file because it is on the CDN.
由于博客文件位于CDN上，因此博客服务器上的大量缓存清除将无助于刷新缓存文件。
The only way would be to “invalidate” the file, which will signal the CDN to pull a fresh copy from the origin location.
唯一方法是使文件“无效”，这将指示CDN从原始位置提取新副本。
But this necessitates you to log on to the CDN server, locate the file, generate a proper invalidation request, and wait for it to percolate to all the mirrors.
但这需要您登录CDN服务器，找到文件，生成适当的失效请求，然后等待其渗透到所有镜像。
And it often costs money.
而且通常要花钱。
CDN Buster offers a much easier alternative.
CDN Buster提供了更简单的替代方法。
You enter a Version String in the plugin admin page, and append the same string where you define the CDN address in your caching plugins, such as WP Super Cache or W3 Total Cache.
您在插件管理页面中输入版本字符串，并在缓存插件（如WP Super Cache或W3 Total Cache）中定义CDN地址的位置附加相同的字符串。
This way, when your reader loads a page, he is looking for a different file, and your CDN server will query your blog server for it, where this plugin will intercept the query and serve the modified file from the original这样，当您的读者加载页面时，他正在寻找一个不同的文件，您的CDN服务器将向您的博客服务器查询该文件，该插件将拦截该查询并提供来自原始的修改后的文件em> location.
em>位置。
Thus, the modified file will get loaded on your CDN and all will be well.
这样，修改后的文件将被加载到您的CDN上，一切都会很好。
Pro Version
专业版
In addition to the fully functional Lite version, CDN Buster also has a Pro version with many more features.
CDN缓存很容易失效，价格为$ 5.95“ rel =” nofollow“>专业版，具有更多功能。
- Automatically update the CDN settings in your WP Super Cache or W3 Total Cache plugin.
- 自动更新WP Super Cache或W3 Total Cache插件中的CDN设置。
- Change the origin pull location on your CDN server to a generic string (eg
cdn-bustor-* where * can be anything) without touching your blog settings to invalidate - 将您的CDN服务器上的原点拉位置更改为通用字符串（例如，
cdn-bustor-* ，其中 * 可以是任何内容），而无需触摸您的博客设置即可使之无效the cache.
缓存。
- Invalidate by file type, so that only certain types of files are invalidated.
- 按文件类型无效，以便仅某些类型的文件无效。
- Invalidate single files from a list that you specify.
- 使您指定的列表中的单个文件无效。
Why use a CDN
为什么要使用CDN
Content Delivery Network (CDN) is a collection of geographically distributed servers that mirror and serve you static contents (images, JavaScrip/CSS files, movies etc.) to your readers much faster than your own blog server can.
Content Delivery Network（CDN）是地理位置分散的服务器的集合，这些服务器可以以比您自己的博客服务器更快的速度向您的读者镜像并向您提供静态内容（图像，JavaScrip / CSS文件，电影等）。
It speeds up your blog tremendously:
它极大地提高了您的博客速度：
- It serves a large part of your website payload from servers that are close to the readers.
- 它从靠近读者的服务器中获取网站负载的很大一部分。
CDN servers are specifically optimized for such contents.
CDN服务器专门针对此类内容进行了优化。
- Since your resources on the CDN have different address (URL), the reader’s browser loads the statc content and the dynamic content (from your blog server) in parallel, enhancing the user experience.
- 由于您在CDN上的资源具有不同的地址（URL），因此阅读器的浏览器并行加载statc内容和动态内容（来自您的博客服务器），从而改善了用户体验。
- The load on your blog server goes down becuase it is no longer serving a large part of the page content, which improves its performance.
- 博客服务器上的负载减少了，因为它不再提供大部分页面内容，从而提高了其性能。
In short, if you are not using a CDN yet, you should.
简而言之，如果您尚未使用CDN，则应该使用。
It is very easy to set it up if you use any popular cacching plugins (such as WP Super Cache or W3 Total Cache).
如果使用任何流行的缓存插件（例如WP Super Cache或W3 Total Cache），则设置起来非常容易。
Most CNDs are of the so-called Origin Pull kind, where the CDN server automatically pulls a file from a location (typically your blog itself) whenever it is asked to serve a file it doesn’t have in its cache.
大多数CND都是所谓的Origin Pull，即CDN服务器在要求提供其缓存中没有的文件时，会自动从某个位置（通常是您的博客本身）中拉出文件。
This is usually a one-time operation, which is slow.
通常这是一次性操作，很慢。
The CDN then proceeds to mirror the file on its servers all over the world.
然后，CDN继续在世界各地的服务器上镜像文件。
Thereafter, whenever the file is requested, the file is served instantly from a server closest to the reader.
此后，无论何时请求文件，都会从距离阅读器最近的服务器立即提供文件。
