WP Manifestindependent plugin directory
manifest / performance / varnish-extended

Varnish Extended WP RegistryNo security issues foundOpen the reportA

Extends Varnish HTTP Purge to purge the cache on multiple backends.

by required · github.com/wearerequired/varnish-extended

★ 0stars
3.7kcomposer installs
1.0.1latest · 8 years ago

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/wearerequired/varnish-extended/archive/refs/heads/master.zip

On Packagist as wearerequired/varnish-extended:

composer require wearerequired/varnish-extended
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
Readme github.com/wearerequired/varnish-extended ↗

Extends Varnish HTTP Purge to purge the cache on multiple backends.

Installation

  1. Install the plugin.
  2. Define VARNISH_BACKENDS in your wp-config.php file. Example: define( 'VARNISH_BACKENDS', [ '127.0.0.1:6081', '127.0.0.2:6081' ] );. Or use the varnish_extended.varnish_backends filter.

Releases

2 releases.

Tag
Published
1.0.1 latest
Jan 13, 2018 8 years ago
1.0.0
Dec 8, 2017 8 years ago

These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.

A grade

Security

Varnish Extended 1.0.1 · audited by WP Registry

No security issues found.

Audited release
1.0.1
Findings
none
Worst severity
—
Content hash
e798d97f49eed53b7a1059e9…

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.

Full report on WP Registry →