Milan Dinić

<a href="http://blog.milandinic.com/wordpress/plugins/purge-cache-for-cloudflare/" rel="nofollow ugc">Plugin homepage</a> | <a href="http://blog.milandinic.com/" rel="nofollow ugc">Plugin author</a> | <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">Premium Version</a> | <a href="http://blog.milandinic.com/donate/" rel="nofollow ugc">Donate</a>
Purge Cache for CloudFlare is a simple plugin that uses CloudFlare® API to purge cache of full HTML pages when a new post is made.
This free version is only indended for basic usage. If you want to use it in full capacity, consider buying <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.
It works by purging front page, post’s page, and main RSS feed. This should work for most sites. However, there are of filters, actions, and methods that provide full customizability and extensibility.
Note that this plugin also sets cache to 30 minutes for all frontend pages. This means that if you use default option in CloudFlare, it tells them to revalidate page cache after that time, so it means that cache for any page expires on CloudFlare servers after that time.
You can change this limits by using filters from you code. If you want user interface in your admin, use <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.
You should create new CloudFlare page rules to set proper caching. It is your responsibility to set this properly.
First page rule should exclude certain paths from caching. Recommended value for this is <code>wp-</code>. This excludes admin pages and default <code>.php</code> pages. Example of URL pattern: <code>*example.com/*wp-*</code> This value can also set via filter or via admin in <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.
Second page rule should sets caching. You need to set “Custom caching” to “Cache everything”. Recommended value for “Edge cache expire TTL” is default, “Respect all existing headers” which means that CloudFlare revalidates after 30 minutes, while for “Browser cache expire TTL” is also 30 minutes. Example of URL pattern: <code>*example.com/*</code>
This plugin is on <a href="https://github.com/dimadin/purge-cache-for-cloudflare" rel="nofollow ugc">GitHub</a> too.
Purge Cache for CloudFlare is in no way affiliated with CloudFlare. It is only using CloudFlare API to purge page cache of certain URLs. 
CloudFlare is registered trademark of CloudFlare, Inc.

Purge Cache for CloudFlare

Simple full HTML page cache purger for CloudFlare.

Zack Tollman

Purgely manages caching behavior for WordPress sites using Fastly as an edge caching solution. The plugin exposes useful 
APIs to help control how pages on your site are cached, as well as provides sane defaults to make this a plug and play 
solution for Fastly cache management.
The plugin handles the following:
<ul>
<li>Sets the <code>Surrogate-Control</code> header to control the expiration time for pages</li>
<li>Sets the <code>stale-while-revalidate</code> and <code>stale-if-error</code> <code>Cache-Control</code> directives for managing these special Fastly 
behaviors</li>
<li>Set groups of <code>Surrogate-Keys</code> for all pages to provide purging across multiple pages with one command</li>
<li>Provides invalidation of posts and related posts on save</li>
</ul>
Each of these items have sane defaults with ways to override them and configure them to your liking.
Additionally, the plugin exposes a WP CLI command to provide more flexible purging options.

Purgely

A plugin to manage Fastly caching behavior and purging.

Purge Cache for CloudFlare vs Purgely