[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f4VSQN-ew8MndrM0hD8WZZ5X-_IIsSpvcC4gp8rxA_ko":3,"$fQbp96BEatQCXBARHhwuZbrbvYEdbOwu9-Dm-p0CsgJ4":177,"$fRJLQzqwLcEpxnUV51_iBB4utsewyCU-ZQZY2xx7CxwM":182},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":24,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"discovery_status":30,"vulnerabilities":31,"developer":32,"crawl_stats":28,"alternatives":38,"analysis":136,"fingerprints":161},"smart-varnish","Smart Varnish","1.0.2","Smartpixels","https:\u002F\u002Fprofiles.wordpress.org\u002Fsmartpixels\u002F","\u003Cp>\u003Ca href=\"http:\u002F\u002Fwww.smartpixels.net\u002F?post_type=products&p=628\" rel=\"nofollow ugc\">Smart Varnish\u003C\u002Fa> A simple plugin to bypass varnish caching for logged in users and serve uncached content.\u003C\u002Fp>\n\u003Cp>Useful for websites that don’t want to serve cached content for logged in users and at the same time want to serve cached content to guests.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE:\u003C\u002Fstrong> This plugin requires knowledge of varnish caching and server administration, it will not work out of the box. We cannot guarantee it will work in every scenario and recommend usage with discretion.\u003C\u002Fp>\n\u003Cp>Please follow the \u003Cstrong>\u003Ca href=\"http:\u002F\u002Fwww.smartpixels.net\u002F?p=650\" rel=\"nofollow ugc\">tutorial here\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>\n","Varnish cache bypass plugin.",10,1868,100,2,"2016-08-30T06:35:00.000Z","4.6.0","3.5","",[20,21,22,23],"varnish","varnish-bypass","varnish-cache","varnish-caching","http:\u002F\u002Fwww.smartpixels.net\u002Fproducts\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsmart-varnish.1.0.2.zip",85,0,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":34,"avg_security_score":26,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"smartpixels",20,30,84,"2026-05-19T21:00:54.971Z",[39,61,82,97,118],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":13,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":18,"download_link":57,"security_score":58,"vuln_count":59,"unpatched_count":27,"last_vuln_date":60,"fetched_at":29},"clp-varnish-cache","CLP Varnish Cache","1.1.1","CloudPanel","https:\u002F\u002Fprofiles.wordpress.org\u002Fcloudpanel\u002F","\u003Cp>Under Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> CLP Varnish Cache or by clicking on the top menu, you can configure CLP Varnish Cache and perform purges.\u003C\u002Fp>\n\u003Ch3>Get Involved\u003C\u002Fh3>\n\u003Cp>Development happens \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcloudpanel-io\u002Fclp-wp-varnish-cache\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>Supports happens on \u003Ca href=\"https:\u002F\u002Fdiscord.cloudpanel.io\" rel=\"nofollow ugc\">Discord\u003C\u002Fa>.\u003C\u002Fp>\n","CLP Varnish Cache lets you configure the cache lifetime, paths, and parameters to exclude from caching. You can purge single urls or cache entries by  …",10000,66840,6,"2026-03-17T14:52:00.000Z","6.9.4","6.0","7.1",[55,56,20,22],"cache","caching","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclp-varnish-cache.1.1.1.zip",99,1,"2026-01-26 00:00:00",{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":69,"downloaded":70,"rating":27,"num_ratings":27,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":18,"tags":74,"homepage":18,"download_link":79,"security_score":80,"vuln_count":59,"unpatched_count":59,"last_vuln_date":81,"fetched_at":29},"varnish-wp","Varnish WordPress","1.7","AdminGeekZ","https:\u002F\u002Fprofiles.wordpress.org\u002Fadmingeekz\u002F","\u003Cp>This is a plugin for wordpress to intergrate the varnish cache for high performance websites.\u003C\u002Fp>\n\u003Cp>This plugin will purge the cache on,\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Post changes (new, edit, trash, delete).\u003C\u002Fli>\n\u003Cli>Page changes (add, edit, remove)\u003C\u002Fli>\n\u003Cli>Comment changes (add, edit, approve,  unapprove,  spam,  trash,  delete)\u003C\u002Fli>\n\u003Cli>Theme changes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cp>At present some of the features are,\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Multiple varnish backends\u003C\u002Fli>\n\u003Cli>Manually purge the cache\u003C\u002Fli>\n\u003Cli>Enable\u002FDisable Feed Purging\u003C\u002Fli>\n\u003Cli>Ability to purge entire cache on changes\u003C\u002Fli>\n\u003Cli>Debug logging\u003C\u002Fli>\n\u003Cli>Minimize number of purges and remove duplicate purges for speed on larger installations\u003C\u002Fli>\n\u003Cli>Supports varnish 4 + 5\u003C\u002Fli>\n\u003Cli>Support for Woocommerce\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Speed\u003C\u002Fh4>\n\u003Cp>Our tests show that by utilizing varnish you gain a ~70x capacity increase over standard WordPress making you resistant to traffic floods (slashdot,  digg, reddit,  stumbleupon).\u003C\u002Fp>\n","This plugin enables you to use the Varnish cache with WordPress,  designed for high performance websites.",70,4470,"2018-02-20T12:15:00.000Z","4.9.29","3.4",[75,22,76,77,78],"high-performance-wordpress","varnish-wordpress","wordpress-cache","wordpress-varnish","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvarnish-wp.1.7.zip",64,"2025-03-31 00:00:00",{"slug":83,"name":84,"version":6,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":11,"downloaded":89,"rating":27,"num_ratings":27,"last_updated":90,"tested_up_to":91,"requires_at_least":92,"requires_php":18,"tags":93,"homepage":95,"download_link":96,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"is-varnish-working","Is Varnish Working?","Oliver Whysall","https:\u002F\u002Fprofiles.wordpress.org\u002Foliverrrwhysall\u002F","\u003Cp>Test your wordpress url to see if it contains the Varnish Cache HTTP headers using the API available at https:\u002F\u002Fisvarnishworking.co.uk\u003C\u002Fp>\n","Test your wordpress url to see if it contains the Varnish Cache HTTP headers",1386,"2021-06-29T22:24:00.000Z","5.7.15","3.0.1",[83,94,20,22],"test-varnish","https:\u002F\u002Fisvarnishworking.co.uk","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fis-varnish-working.1.0.2.zip",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":105,"downloaded":106,"rating":107,"num_ratings":108,"last_updated":109,"tested_up_to":51,"requires_at_least":110,"requires_php":111,"tags":112,"homepage":116,"download_link":117,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"varnish-http-purge","Proxy Cache Purge","5.9.0","Danila Vershinin","https:\u002F\u002Fprofiles.wordpress.org\u002Fdvershinin\u002F","\u003Cp>\u003Cstrong>This plugin \u003Cem>does not\u003C\u002Fem> install nor configure a cache proxy. It acts as an interface with such services.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>One common method of caching content for websites is via the use of reverse proxy caching. Common examples of this are \u003Ca href=\"https:\u002F\u002Fwww.varnish-cache.org\u002F\" rel=\"nofollow ugc\">Varnish\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwww.nginx.org\u002F\" rel=\"nofollow ugc\">NGINX\u003C\u002Fa>. These systems allow a website to update content and have the visitor’s experience cached without the need for complex plugins storing the files locally and using up a user’s disk space.\u003C\u002Fp>\n\u003Cp>A reverse proxy cache is installed in front of a server and reviews requests. If the page being requested is already cached, it delivers the cached content. Otherwise it generates the page and the cache on demand.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Proxy Cache Purge plugin sends a request to delete (aka flush) the cached data of a page or post every time it’s modified.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Cp>When content on a site is updated by WordPress, the plugin reaches out to the proxy cache service with the URL of the page, requesting the cache be deleted.\u003C\u002Fp>\n\u003Cp>Not all pages are deleted from the cache on every change. For example, when a post, page, or custom post type is edited, or a new comment is added, \u003Cem>only\u003C\u002Fem> the following pages will purge:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The front page\u003C\u002Fli>\n\u003Cli>The post\u002Fpage edited\u003C\u002Fli>\n\u003Cli>Any categories, tags, and\u002For custom taxonomies associated with the page\u003C\u002Fli>\n\u003Cli>Related feeds\u003C\u002Fli>\n\u003Cli>Associated JSON API pages\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition, your \u003Cem>entire\u003C\u002Fem> cache will be deleted on the following actions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Changing themes\u003C\u002Fli>\n\u003Cli>Pressing the \u003Cstrong>Empty Cache\u003C\u002Fstrong> button on the toolbar\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Plugins can hook into the purge actions as well, to filter their own events to trigger a purge.\u003C\u002Fp>\n\u003Cp>On a multisite network using subfolders, only \u003Cstrong>network admins\u003C\u002Fstrong> can purge the main site.\u003C\u002Fp>\n\u003Ch4>Development Mode\u003C\u002Fh4>\n\u003Cp>If you’re working on a site and need to turn off caching in one of two ways:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Add \u003Ccode>define( 'VHP_DEVMODE', true );\u003C\u002Fcode> to your \u003Ccode>wp-config.php\u003C\u002Fcode> file\u003C\u002Fli>\n\u003Cli>Go to Proxy Cache -> Settings and enable Debug Mode for 24 hours at a time\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>That will break cache on page loads. It is \u003Cem>not\u003C\u002Fem> recommended for production!\u003C\u002Fp>\n\u003Ch4>Cache Tags (BETA)\u003C\u002Fh4>\n\u003Cp>As of version 5.4.0, Proxy Cache Purge includes an \u003Cstrong>optional Cache Tags \u002F Surrogate Keys purge mode\u003C\u002Fstrong>. This feature is marked as \u003Cstrong>BETA\u003C\u002Fstrong> and is disabled by default.\u003C\u002Fp>\n\u003Cp>When enabled, the plugin:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Adds cache-tag headers to WordPress responses (for example, tagging pages by post ID, post type, taxonomy terms, author, and archives).\u003C\u002Fli>\n\u003Cli>Uses tag-based purges instead of individual URL purges when content is updated, which can reduce purge traffic and improve consistency on complex sites.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Requirements:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A proxy cache that supports Cache Tags \u002F Surrogate Keys and advertises this via standard \u003Ccode>Surrogate-Capability\u003C\u002Fcode> headers (for example, \u003Ccode>Surrogate-Capability: vhp=\"Surrogate\u002F1.0 tags\u002F1\"\u003C\u002Fcode>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>How to enable:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Go to \u003Cstrong>Proxy Cache \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Purge Method\u003C\u002Fstrong> and check \u003Cstrong>“Use Cache Tags (Surrogate Keys)”\u003C\u002Fstrong>. The checkbox is only enabled when your cache tells WordPress it supports tags (or when you explicitly enable it via a define).\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Alternatively, you can force-enable or force-disable detection via \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cp>define( ‘VHP_VARNISH_TAGS’, true );  \u002F\u002F Force treat cache as tag-capable\u003Cbr \u002F>\ndefine( ‘VHP_VARNISH_TAGS’, false ); \u002F\u002F Force treat cache as not tag-capable\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because this feature depends on your cache configuration, it is recommended that you test it carefully in staging before enabling it on production.\u003C\u002Fp>\n\u003Ch4>Background Purging with WP-Cron\u003C\u002Fh4>\n\u003Cp>On busy sites, sending many PURGE requests directly from admin requests can slow things down. When you define \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> as \u003Ccode>true\u003C\u002Fcode> in \u003Ccode>wp-config.php\u003C\u002Fcode> (because you are running a real system cron that calls \u003Ccode>wp-cron.php\u003C\u002Fcode>), Proxy Cache Purge automatically switches to an asynchronous mode:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Purge requests (both URL-based and tag-based, when Cache Tags are enabled) are collected into a small per-site queue.\u003C\u002Fli>\n\u003Cli>The queue is processed by WP-Cron in the background, keeping your admin and content-editing actions responsive even when many URLs or tags must be invalidated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Object-cache purges (the “Purge Database Cache” option) remain synchronous and are not affected by this behaviour. The Proxy Cache settings page and Site Health integration expose basic queue status so you can verify that background purging is healthy; if the queue appears large or very old, check that your system cron is correctly invoking WordPress cron.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important: Cron Frequency and Cache Freshness\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When using background purging, the frequency of your system cron determines how quickly cache invalidations are processed. The longer the interval between cron runs, the longer visitors may see stale content after updates.\u003C\u002Fp>\n\u003Cp>For minimal stale content, run your system cron every minute:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>* * * * * \u002Fusr\u002Fbin\u002Fphp \u002Fvar\u002Fwww\u002Fhtml\u002Fwp-cron.php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you can tolerate slightly longer delays, every 2-5 minutes is also acceptable. However, running cron less frequently (e.g., every 15 minutes) means cache purges may be delayed by that amount after content changes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> Scheduled posts are handled specially. When a scheduled post is published via WP-Cron, the cache is purged synchronously within the same cron run, ensuring immediate cache invalidation without waiting for the next cron execution.\u003C\u002Fp>\n\u003Cp>For detailed instructions on setting up a proper Linux-based WordPress cron, see: \u003Ca href=\"https:\u002F\u002Fwww.getpagespeed.com\u002Fweb-apps\u002Fwordpress\u002Fwordpress-cron-optimization\" rel=\"nofollow ugc\">WordPress Cron Optimization\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Disabling Background Purging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you have \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> defined but do not want background purging (for example, on low-traffic sites where immediate purges are preferred), you can force-disable cron-based purging by adding this to your \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'VHP_DISABLE_CRON_PURGING', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>With this constant set, all cache purges will execute immediately during the request, regardless of the \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> setting.\u003C\u002Fp>\n\u003Ch3>WP-CLI\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Purge\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Purge commands let you empty the cache.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish purge\u003C\u002Fcode> – Flush the entire site cache (equivalent to clicking “Empty Cache” in admin)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --all\u003C\u002Fcode> – Explicitly flush the entire site cache\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge \u003Curl>\u003C\u002Fcode> – Flush cache for a specific URL and all content below it (wildcard)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge \u003Curl> --url-only\u003C\u002Fcode> – Flush cache for only the exact URL specified (no wildcard)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=\u003Ctag>\u003C\u002Fcode> – Flush cache by tag (requires Cache Tags mode to be enabled)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish purge\u003C\u002Fcode> – Purge entire site\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --all\u003C\u002Fcode> – Same as above, more explicit\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fhello-world\u002F\u003C\u002Fcode> – Purge this URL and everything below it\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fhello-world\u002F --url-only\u003C\u002Fcode> – Purge only this exact URL\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fwp-content\u002Fthemes\u002F --wildcard\u003C\u002Fcode> – Purge all theme files\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=p-123\u003C\u002Fcode> – Purge all pages tagged with post ID 123\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=pt-post\u003C\u002Fcode> – Purge all cached pages of post type “post”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Debug\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Debugging can help you figure out why your cache isn’t working as well as it could. The default is for your home page, but you can pass any URL on your domain.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish debug [\u003Curl>]\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Available parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[--include-headers]\u003C\u002Fcode> —  Include headers in debug check output\u003C\u002Fli>\n\u003Cli>\u003Ccode>[--include-grep]\u003C\u002Fcode> — Grep active theme and plugin directories for common issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>DevMode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Development mode allows you to disable the cache, temporarily.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish devmode [\u003Cactivate|deactivate|toggle>]\u003C\u002Fcode> – Change development mode state\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Async purge queue (cron-mode)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you define \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> as \u003Ccode>true\u003C\u002Fcode> and run a real system cron for WordPress, Proxy Cache Purge can move heavy purge work into a small background queue that is processed by WP‑Cron.\u003C\u002Fp>\n\u003Cp>You can inspect and manage that queue via WP‑CLI:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish queue status\u003C\u002Fcode> – show whether cron-mode is active, if a full purge is queued, counts of queued URLs\u002Ftags, and the last queue run time.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish queue process\u003C\u002Fcode> – process any items currently in the queue (useful to run after deploys or cache‑sensitive operations).\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish queue clear\u003C\u002Fcode> – clear the queue without sending any PURGE requests.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These commands do not replace your normal WordPress cron (you still need a cron entry that calls \u003Ccode>wp cron event run --due-now\u003C\u002Fcode> or hits \u003Ccode>wp-cron.php\u003C\u002Fcode>), but they give you a simple operational handle when using cron‑mode.\u003C\u002Fp>\n\u003Ch4>Understanding Purge Behavior\u003C\u002Fh4>\n\u003Cp>There are different types of cache purges, and they behave differently:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Manual Purges (Admin Bar)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>“Purge Cache (All Pages)”\u003C\u002Fstrong> – Sends a single regex purge request to invalidate the entire cache. Always executes immediately.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>“Purge Cache (this page)”\u003C\u002Fstrong> – Purges only the exact URL you’re viewing. Always executes immediately.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Manual purges are always immediate, even when background cron-mode is enabled. This is intentional: when you click a button, you expect immediate results.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Automatic Purges (Post Save\u002FUpdate)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you save or update a post, the plugin automatically purges:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The post’s URL\u003C\u002Fli>\n\u003Cli>The homepage\u003C\u002Fli>\n\u003Cli>Category archive pages\u003C\u002Fli>\n\u003Cli>Tag archive pages\u003C\u002Fli>\n\u003Cli>Author archive page\u003C\u002Fli>\n\u003Cli>Date-based archives\u003C\u002Fli>\n\u003Cli>RSS feeds\u003C\u002Fli>\n\u003Cli>Related REST API endpoints\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This can be 20-50+ URLs depending on your site structure. When cron-mode is enabled, these automatic purges are queued and processed in the background to avoid slowing down the post editor.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Difference\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>  Action\u003Cbr \u002F>\n  URLs Purged\u003Cbr \u002F>\n  Uses Cron Queue?\u003C\u002Fp>\n\u003Cp>  “Purge Cache (All Pages)”\u003Cbr \u002F>\n  1 (regex)\u003Cbr \u002F>\n  No – always immediate\u003C\u002Fp>\n\u003Cp>  “Purge Cache (this page)”\u003Cbr \u002F>\n  1\u003Cbr \u002F>\n  No – always immediate\u003C\u002Fp>\n\u003Cp>  Post save\u002Fupdate\u003Cbr \u002F>\n  20-50+\u003Cbr \u002F>\n  Yes (if cron-mode enabled)\u003C\u002Fp>\n\u003Cp>If you need to immediately purge all URLs related to a specific post (not just the post URL), save the post – the automatic purge will handle all related URLs.\u003C\u002Fp>\n","Automatically empty proxy cached content when your site is modified.",40000,2241997,88,26,"2026-04-02T16:12:00.000Z","5.0","5.6",[55,113,114,115,20],"nginx","proxy","purge","https:\u002F\u002Fgithub.com\u002Fdvershinin\u002Fvarnish-http-purge","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvarnish-http-purge.5.9.0.zip",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":126,"downloaded":127,"rating":13,"num_ratings":11,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":18,"tags":131,"homepage":18,"download_link":133,"security_score":134,"vuln_count":59,"unpatched_count":59,"last_vuln_date":135,"fetched_at":29},"purge-varnish","Purge Varnish Cache","2.6","Dsingh","https:\u002F\u002Fprofiles.wordpress.org\u002Fdevavi\u002F","\u003Cp>Purge Varnish Cache provides integration between your WordPress site and multiple Varnish Cache servers. Purge Varnish Cache sends a PURGE request to the URL of a page or post every time based on configured actions and trigger by site administrator. Varnish is a web application accelerator also known as a caching HTTP reverse proxy.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003Cbr \u002F>\n*   Support on all varnish versions of 3.x, 4.x, 5.x and 6.x\u003Cbr \u002F>\n*   One time configuration.\u003Cbr \u002F>\n*   admin-socket integration and Varnish admin interface for status.\u003Cbr \u002F>\n*   unlimited number of Varnish Cache servers.\u003Cbr \u002F>\n*   Custom URLs purge.\u003Cbr \u002F>\n*   User interface for manual purge.\u003Cbr \u002F>\n*   Single click entire cache purge.\u003Cbr \u002F>\n*   Debugging.\u003Cbr \u002F>\n*   Actively maintained.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Requirements:\u003C\u002Fstrong> Apache sockets module\u002Fextention should be enabled.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Purpose:\u003C\u002Fstrong> The main purpose of developing this plugin is to deliver updated copy of content to end user without any delay.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enhancement Request:\u003C\u002Fstrong> For any further enhancement, please mail me at \u003Ca href=\"mailto:dev.firoza@gmail.com\" rel=\"nofollow ugc\">\u003Cstrong>dev.firoza@gmail.com\u003C\u002Fstrong>\u003C\u002Fa>\u003C\u002Fp>\n","Clean clear VARNISH cache automatically when content on your site is created or modified, also allow you to purge VARNISH cache manually.",2000,56556,"2024-02-04T11:15:00.000Z","6.3.8","4.0",[55,56,132,115,20],"flush","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpurge-varnish.1.1.4.zip",63,"2025-09-05 00:00:00",{"attackSurface":137,"codeSignals":149,"taintFlows":156,"riskAssessment":157,"analyzedAt":160},{"hooks":138,"ajaxHandlers":145,"restRoutes":146,"shortcodes":147,"cronEvents":148,"entryPointCount":27,"unprotectedCount":27},[139],{"type":140,"name":141,"callback":142,"file":143,"line":144},"action","init","smart_varnish_init","smart_varnish.php",74,[],[],[],[],{"dangerousFunctions":150,"sqlUsage":151,"outputEscaping":153,"fileOperations":27,"externalRequests":27,"nonceChecks":27,"capabilityChecks":27,"bundledLibraries":155},[],{"prepared":27,"raw":27,"locations":152},[],{"escaped":27,"rawEcho":27,"locations":154},[],[],[],{"summary":158,"deductions":159},"The smart-varnish plugin v1.0.2 exhibits an excellent security posture based on the provided static analysis. There are no identified entry points in the form of AJAX handlers, REST API routes, shortcodes, or cron events, which significantly limits the potential attack surface. Furthermore, the code signals indicate a complete absence of dangerous functions, file operations, and external HTTP requests. All SQL queries utilize prepared statements, and all output is properly escaped, demonstrating strong secure coding practices. The lack of identified taint flows also suggests that data handling within the plugin is robust against common injection vulnerabilities.  The vulnerability history is also clean, with no recorded CVEs, further reinforcing its secure standing. This plugin appears to be developed with a strong focus on security.",[],"2026-04-16T12:21:04.374Z",{"wat":162,"direct":169},{"assetPaths":163,"generatorPatterns":165,"scriptPaths":166,"versionParams":167},[164],"\u002Fwp-content\u002Fplugins\u002Fsmart-varnish\u002Fjs\u002Fsmart-varnish.js",[],[164],[168],"smart_varnish\u002Fjs\u002Fsmart-varnish.js?ver=",{"cssClasses":170,"htmlComments":171,"htmlAttributes":172,"restEndpoints":173,"jsGlobals":174,"shortcodeOutput":176},[],[],[],[],[175],"smart_varnish_bypass",[],{"error":178,"url":179,"statusCode":180,"statusMessage":181,"message":181},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fsmart-varnish\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":14,"versions":183},[184,190],{"version":6,"download_url":25,"svn_tag_url":185,"released_at":28,"has_diff":186,"diff_files_changed":187,"diff_lines":28,"trac_diff_url":188,"vulnerabilities":189,"is_current":178},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fsmart-varnish\u002Ftags\u002F1.0.2\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fsmart-varnish%2Ftags%2F1.0.0&new_path=%2Fsmart-varnish%2Ftags%2F1.0.2",[],{"version":191,"download_url":192,"svn_tag_url":193,"released_at":28,"has_diff":186,"diff_files_changed":194,"diff_lines":28,"trac_diff_url":28,"vulnerabilities":195,"is_current":186},"1.0.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsmart-varnish.1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fsmart-varnish\u002Ftags\u002F1.0.0\u002F",[],[]]