/ Plugin Category

/ Performance & Optimization

/ Caching Solutions

/ Proxy Cache Purge

Proxy Cache Purge

By Danila Vershinin

Performance & Optimization / Caching Solutions

Proxy Cache Purge Review - In-Depth Analysis

Automatically empties proxy cached content when your site is modified.

Performance Overview

WPS Score

6.99/10

User Rating

4.4/5 (based on 26+ reviews)

Active Installations

40,000+

Update Frequency

Average It is calculated using the weighted average of same category plugins.

Security Score

1 / 10 (Very Low Risk) It is calculated using the weighted average of all versions.

What It Does

This plugin does not install nor configure a cache proxy. It acts as an interface with such services. One common method of caching content for websites is via the use of reverse proxy caching, such as Varnish and NGINX. These systems allow a website to update content while caching the visitor's experience without using up a user's disk space.

The Proxy Cache Purge plugin sends a request to delete the cached data of a page or post every time it is modified. When content on a site is updated, the plugin reaches out to the proxy cache service with the URL of the page, requesting the cache be deleted.

Not all pages are deleted from the cache on every change. For example, when a post or page is edited, only specific pages will be purged, including the front page and the post/page edited. The entire cache will be deleted on certain actions, such as changing themes or pressing the Empty Cache button.

Comparing to Alternatives

Proxy Cache Purge is a straightforward plugin designed to manage Varnish cache purging efficiently. Compared to alternatives like CLP Varnish Cache, it focuses on simplicity and reliability.

Top alternatives

CLP Varnish Cache ( WPS: 6.98)

Strengths

Simple and effective cache purging for Varnish.
Minimal interference when not in use.
Compatible with various cache servers.
Lightweight and easy to configure.

Weaknesses

Limited documentation and support resources.
Lacks advanced features found in some alternatives.
Compatibility issues with certain server setups like remote NGINX reverse proxy.
Does not actively support latest PHP versions.

User Sentiment Analysis

User feedback highlights the plugin's reliability and ease of use, though some technical issues and compatibility concerns are noted.

Positive highlights

"Thanks for bringing out this plugin! Varnish can be quite 'dogged' in its caching, this plugin solves it very nicely." - Dave Loodts
"ОТЛИЧНО, СПАСИБО ВАМ!" - senatmedia
"No complaints, it’s been working perfectly for years." - random9q
"The plugin simply works even for all types of cache servers." - Skrlance
"I had a lot of problems with cache but this solved them! Thank you." - manuamaro

Common complaints

Issues with missing Age header in responses causing errors.
Limited guidance on expected headers for proper operation.
Compatibility concerns with newer PHP versions.
Lack of support for some reverse proxy configurations.

Weaknesses

Plugin help is insufficient for troubleshooting advanced server setups.
Does not update to support latest PHP versions recommended by WordPress.

Who Should Use This?

Best for

Users running Varnish cache who need a simple, reliable plugin to purge cache without extra complexity.

Not ideal for

Users requiring advanced cache management features or those with complex server environments needing extensive support and compatibility.

Pricing & Value

Free version includes

The free version provides essential cache purging functionality for Varnish without any cost, suitable for most standard use cases.

Final Verdict

Proxy Cache Purge is a dependable and straightforward solution for managing Varnish cache purging, praised for its simplicity and effectiveness by many users.

However, it has limitations in documentation, advanced features, and compatibility with newer PHP versions, which may affect users with more complex needs.

Other Notable Features

Here are a few other notable features of this free Proxy Cache Purge plugin.

Cache

Nginx

Proxy

Purge

Varnish

Screenshots

FAQ

This plugin was originally adopted and updated for DreamHost’s DreamPress server, however it is not (and never has been) for DreamHost only.

I worked at DreamHost from 2012 to 2022, and have maintained the plugin since around 2014 or so.

As of October 2023, this plugin is NO LONGER installed by default on DreamPress.

Today, the plugin is maintained by GetPageSpeed, with a focus on advanced NGINX and proxy caching deployments and strong compatibility with the NGINX cache-purge module from the NGINX Extras collection.

Yes. If your environment doesn’t cache logged-in users and you want to avoid purge noise from autosaves/drafts, you can exclude specific statuses network‑wide via wp-config.php (multisite‑friendly).

Add a define to exclude drafts:

define( 'VHP_EXCLUDED_POST_STATUSES', 'draft' );

Exclude multiple statuses (comma‑separated):

define( 'VHP_EXCLUDED_POST_STATUSES', 'draft,pending' );

Or pass an array:

define( 'VHP_EXCLUDED_POST_STATUSES', array( 'draft', 'pending' ) );

Developers can also use a filter to adjust the valid statuses programmatically:

add_filter( 'varnish_http_purge_valid_post_statuses', function( $statuses, $post_id ) {     return array_diff( $statuses, array( 'draft' ) ); }, 10, 2 );

By default, the plugin considers these statuses for purge URL generation: publish, private, trash, pending, draft.

Some providers require a control key, token, or Authorization header to accept PURGE requests. You can set a header name and value via the settings page or via the following constant:

define( 'VHP_VARNISH_EXTRA_PURGE_HEADER', 'X-Control-Key: YOUR_CONTROL_KEY_HERE' );

Alternatively, you can inject any required header via a filter.

Set where PURGE requests should be sent (host:port, no scheme):

define( ‘VHP_VARNISH_IP’, ‘varnish.example.com:6081’ );
Add your control key/auth header via a small MU plugin so it loads on every request. Create wp-content/mu-plugins/varnish-purge-auth.php with:

<?php
add_filter( ‘varnish_http_purge_headers’, function( $headers ) {
// Example: provider expects a custom key header
$headers[‘X-Control-Key’] = ‘YOUR_CONTROL_KEY_HERE’;
```
// Or use Authorization headers: // $headers['Authorization'] = 'Basic ' . base64_encode( 'username:password' ); // $headers['Authorization'] = 'Bearer ' . 'YOUR_TOKEN_HERE';  return $headers; 
```
} );

If your provider requires HTTPS for the purge endpoint, force the schema:

add_filter( 'varnish_http_purge_schema', function() { return 'https://'; } );

Important: This plugin sends HTTP PURGE requests to your cache service. It does not use the Varnish management interface (varnishadm/secret on port 6082).

You can use varnish_http_purge_x_varnish_header_name filter to customize this header name, like below to resolve this:

function change_varnish_header( $default_header ) {     return 'My-Custom-Header'; // Replace with the desired header } add_filter( 'varnish_http_purge_x_varnish_header_name', 'change_varnish_header' );