Naibabiji Cache Purger for EdgeOne vs Varnish/Nginx Proxy Caching

A powerful WordPress plugin that automatically purges Tencent Cloud EdgeOne cache when your posts, pages, or custom post types are published, updated, or deleted. External services This plugin connects to the Tencent Cloud EdgeOne API (https://teo.tencentcloudapi.com) to provide cache purging and prefetching functionality. It sends the Following information to Tencent Cloud when a purge or prefetch operation is triggered (e.g., when a post is updated, or when manual purge is used): * Tencent Cloud API Credentials (SecretId): Used for request authentication and signing. * EdgeOne Zone ID: Used to identify the specific site/zone in EdgeOne. * Target URLs or Paths: The specific resources that need to be cleared or prefetched from the CDN nodes. This service is provided by “Tencent Cloud”: Terms of Service, Privacy Policy. Features Automatic Cache Purge Automatically purges cache when posts are published, updated, or deleted Supports all public post types (posts, pages, and custom post types) Smart purge: automatically refreshes post pages, homepage, category archives, tag archives, author archives, and date archives Comment Integration Automatically purges related post cache when new comments are approved Manual Purge Support for manual purge of specific posts or entire site Quick purge buttons in admin panel for recent posts Flexible Configuration Choose purge method: delete cache (delete) or mark as expired (invalidate) Optional logging of purge operations Secure key configuration via wp-config.php constants Cache Plugin Integration Automatically purges EdgeOne cache when popular WordPress cache plugins clear their cache Supports WP Super Cache, W3 Total Cache, WP Rocket, and LiteSpeed Cache Force mode ensures cache plugin integrations work even when auto purge is disabled Proper timing control ensures compatibility with all cache plugin loading sequences Cache Prefetching Optional cache prefetching after purging (disabled by default) Only prefetches post URLs, not archive pages to conserve EdgeOne prefetch quota Ensures first visitor gets cached content immediately Prefetch results are displayed in the purge logs for easy monitoring Enhanced Logging Detailed logging of all purge operations with success/failure status Manual log clearing functionality for easier debugging Prefetch operation results displayed alongside purge results Job IDs and error messages for easy troubleshooting Advanced Manual Purge Optimized host-specific “Purge All” using the purge_host method Manual purge operations are not affected by auto purge settings Force mode support for cache plugin integrations Comprehensive URL coverage for post-related purges Custom URL Purge Purge cache for specific URLs (CSS, JS, images, etc.) Support for directory prefix purge using trailing slash (/) Batch processing: enter multiple URLs, one per line Automatic URL validation and filtering Smart type detection: files use purge_url, directories use purge_prefix Nginx Cache Integration Optionally clear Nginx server-side page cache (FastCGI cache or Proxy cache) alongside EdgeOne CDN cache Configured separately — most sites using only WordPress cache plugins do not need this Nginx cache and EdgeOne cache are cleared independently; either can succeed even if the other fails Includes path validation with real-time feedback in the settings page Uses ngx_cache_purge module for precise URL-based cache clearing (faster and more efficient) Added “Purge Endpoint Path” option for customizable Nginx purge URL path (e.g., use a random string like /xK9mPurge_q7z for better security) Uses HTTPS requests to your site’s own domain for purge, avoiding HTTP-to-HTTPS redirect issues Friendly error messages in purge logs: clearly explains why a URL wasn’t cached (e.g., “Not cached — the page was returned instead of a purge response”) instead of showing raw HTML Fallback to file deletion for full-site purge operations Detailed per-URL purge logging for Nginx cache operations No SDK Required Direct API calls, no need to install Tencent Cloud SDK Compatible with all WordPress versions 5.5+ Configuration Get Tencent Cloud API Keys Visit Tencent Cloud Console Create or get your SecretId and SecretKey Get EdgeOne Zone ID Visit EdgeOne Console Select your site and find the Zone ID (format: zone-xxxxxx) Configure Plugin There are two configuration methods: Method 1: Using wp-config.php (Recommended) Add these constants to your WordPress wp-config.php file: define( 'NB_CACHE_PURGER_SECRET_ID', 'your-secret-id' ); define( 'NB_CACHE_PURGER_SECRET_KEY', 'your-secret-key' ); Then in WordPress admin: 1. Go to “Settings” → “Naibabiji Cache Purger” 2. Fill in the Zone ID (Secret ID and Secret Key will be automatically loaded from constants) 3. Choose other options and save Method 2: Direct Configuration in Admin Log in to WordPress admin Go to “Settings” → “Naibabiji Cache Purger” Fill in the following information: Secret ID: Tencent Cloud API Secret ID Secret Key: Tencent Cloud API Secret Key Zone ID: EdgeOne Zone ID Choose other options: Enable Auto Purge: Whether to automatically purge cache when posts are updated Purge Method: delete: Directly delete node cache invalidate: Mark as expired, revalidate from origin Enable Logging: Whether to log purge operations Nginx Cache Integration (Optional) Only needed if your server uses Nginx FastCGI cache or Proxy cache (configured via fastcgi_cache_path or proxy_cache_path in nginx.conf). Most sites using WordPress cache plugins do not need this. In “Settings” → “Naibabiji Cache Purger” → scroll to the Nginx Cache Integration section at the bottom Check Enable Nginx Cache Purge Set a Purge Endpoint Path — we recommend using a random string (e.g., /xK9mPurge_q7z) for security, so you can use allow all; in Nginx without exposing the endpoint to attackers Enter the absolute filesystem path to your Nginx cache zone directory (e.g. /var/run/nginx-cache) — this is only used as fallback when purging the entire site The web server process (e.g. www-data) must have write permission to this directory The settings page will validate the path and show whether it is writable Save settings — Nginx cache will now be cleared automatically every time EdgeOne cache is purged Nginx Purge Configuration To use the ngx_cache_purge module integration, you need to configure your Nginx server block with the appropriate purge rules. Replace /xK9mPurge_q7z with your custom purge path: nginx location ~ /xK9mPurge_q7z(/.*) { allow all; deny none; fastcgi_cache_purge YOUR_CACHE_ZONE "https$request_method$host$1"; # Or for proxy cache: # proxy_cache_purge YOUR_CACHE_ZONE "https$request_method$host$1"; } Replace YOUR_CACHE_ZONE with the name of your Nginx cache zone (e.g., wordpress). Important notes: * The fastcgi_cache_purge key ("https$request_method$host$1") must match your fastcgi_cache_key directive exactly, including the https prefix * If you are using BT Panel (宝塔) with an HTTP-to-HTTPS redirect rule, the plugin sends HTTPS requests to your own domain, so no additional exclusion rules are needed * For detailed configuration instructions, see the configuration tutorial

Complete WordPress Varnish Cache 3.x/4.x/5.x and Nginx Proxy Cache integration. This plugin handles all integration with Varnish Cache and Nginx Proxy Cache. It was designed for high traffic websites. Main features admin interface, see screenshots console for manual purges, supports regular expressions so you can purge an entire folder or just a single file supports every type of Varnish Cache implementation, see screenshots for examples unlimited number of Varnish Cache servers use of custom headers when communicating with Varnish Cache does not interfere with other caching plugins, cloudflare, etc Varnish Cache configuration generator purge key method so you don’t need to setup ACLs debugging actively maintained You can control the following from the Varnish Caching admin panel : Enable/Disable caching Homepage cache TTL Cache TTL (for every other page) IPs/Hosts to clear cache to support every type of Varnish Cache implementation Override default TTL in posts/pages Purge key based PURGE Logged in cookie Debugging option console for precise manual purges This plugin also auto purges Varnish Cache / Nginx Proxy Cache when your site is modified. Varnish Caching sends a PURGE request to Varnish Cache / Nginx Proxy Cache when a page or post is modified. This occurs when editing, publishing, commenting or deleting an item, and when changing themes. Not all pages are purged every time, depending on your Varnish / Nginx Proxy Cache configuration. When a post, page, or custom post type is edited, or a new comment is added, only the following pages will purge: The front page The post/page edited Any categories or tags associated with the page Varnish Cache / Nginx Proxy Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. This plugin does not install Varnish/Nginx for you, nor does it configure Varnish/Nginx for WordPress. It’s expected you already did that on your own using the provided config files. Inspired from the following : https://wordpress.org/plugins/varnish-http-purge/ https://github.com/dreamhost/varnish-vcl-collection/