[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fhdtlImwKf7OMk7DO73s24HMQXDAJgcAjy4IrL8YFRMg":3},{"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":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":39,"analysis":138,"fingerprints":247},"wao-io-cache-control","wao.io Cache Control","1.0.0","wao.io","https:\u002F\u002Fprofiles.wordpress.org\u002Fwaoio\u002F","\u003Cp>wao.io Cache Control is a free plugin to clear your WordPress site’s cache at \u003Ca href=\"https:\u002F\u002Fwao.io\u002Fen\u002F?utm_source=wordpressMarketplace&utm_medium=description&utm_campaign=CachePlugin\" rel=\"nofollow ugc\">wao.io\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Cache Control\u003C\u002Fh3>\n\u003Cp>Use this plugin to control your site’s cache at wao.io.\u003C\u002Fp>\n\u003Cp>Click on the \u003Cstrong>Invalidate Origin Content\u003C\u002Fstrong> button to clear your optimized WordPress website’s cache at wao.io\u003Cbr \u002F>\nto make sure that you and your customers will see the latest version of your content.\u003C\u002Fp>\n\u003Cp>Cache invalidation will automatically be triggered after publishing or updating a post or a page, and after switching a theme.\u003C\u002Fp>\n\u003Cp>Cache invalidation treats all content in the cache as if it was outdated.\u003Cbr \u002F>\nThis means that wao.io will check on the next request if the content changed on the origin server.\u003Cbr \u002F>\nIf so, it will be requested. Otherwise wao.io will continue to use the cached resource.\u003Cbr \u002F>\nThis is especially useful if you changed only a few images and the majority of content remained unmodified.\u003C\u002Fp>\n\u003Ch3>Settings\u003C\u002Fh3>\n\u003Cp>In the \u003Cstrong>wao.io Cache Control Settings\u003C\u002Fstrong> section of your general WordPress settings,\u003Cbr \u002F>\nplease enter your Site ID, and the API key that you obtained from wao.io’s support team.\u003C\u002Fp>\n\u003Cp>If you do not have an API key yet, please contact \u003Ca href=\"https:\u002F\u002Fwao.io\u002Fen\u002Faccount\u002Fsupport?utm_source=wordpressMarketplace&utm_medium=description&utm_campaign=CachePlugin\" rel=\"nofollow ugc\">wao.io support\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>In future versions of this plugin, you can disable or enable automatic cache invalidation here.\u003C\u002Fp>\n\u003Ch3>Automatic Cache Invalidation\u003C\u002Fh3>\n\u003Cp>Automatic cache invalidation will make WordPress try to invalidate your\u003Cbr \u002F>\noptimized WordPress website’s cache at wao.io automatically each time your content has changed,\u003Cbr \u002F>\ne.g. after publishing a page or uploading an image.\u003C\u002Fp>\n\u003Ch3>Known Issues\u003C\u002Fh3>\n\u003Cp>Some WordPress sites reported a bug that the publish \u002F update post event did not fire when using the block editor (Gutenberg issue #17632).\u003Cbr \u002F>\nThis may affect the plugin wao.io Cache Control which depends on the event for automatic cache invalidation.\u003C\u002Fp>\n\u003Ch3>Development and Contribution\u003C\u002Fh3>\n\u003Cp>wao.io Cache Control plugin for WordPress was developed for wao.io by Ingo Steinke, Senior Software Developer at Avenga Germany GmbH.\u003C\u002Fp>\n\u003Cp>If you want to contribute to this plugin, please contact wao.io product development via our \u003Ca href=\"https:\u002F\u002Fwao.io\u002Fen\u002F?utm_source=wordpressMarketplace&utm_medium=description&utm_campaign=CachePlugin\" rel=\"nofollow ugc\">website wao.io\u003C\u002Fa>.\u003C\u002Fp>\n","wao.io Cache Control is a free plugin to clear your WordPress site's cache at wao.io.",10,1632,100,1,"2020-08-09T13:15:00.000Z","5.5.18","4.8","5.6",[20,21,22,23,24],"cache","caching","clear","control","pagespeed","https:\u002F\u002Fwao.io\u002Fen\u002Ffeatures\u002Floadtime-optimization\u002Fcaching","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwao-io-cache-control.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":27,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},"waoio",2,20,30,84,"2026-04-05T09:23:35.590Z",[40,60,78,97,114],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":28,"num_ratings":28,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":18,"tags":53,"homepage":56,"download_link":57,"security_score":58,"vuln_count":34,"unpatched_count":34,"last_vuln_date":59,"fetched_at":30},"cache-control-by-cacholong","Cache control by Cacholong","5.4.1","Preliot","https:\u002F\u002Fprofiles.wordpress.org\u002Fpreliot\u002F","\u003Cp>“Cache control by Cacholong” plugin automates purging of Nginx Pagespeed cache and Nginx FastCGI cache on your Nginx server(s). It is a backend plugin that is able to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Purge Nginx Pagespeed cache and\u002For Nginx FastCGI cache.\u003C\u002Fli>\n\u003Cli>Purge cache automatically, manually, with WordPress cronjobs and WP-CLI.\u003C\u002Fli>\n\u003Cli>Purge caches on one or more servers (See hosts.json section for more details).\u003C\u002Fli>\n\u003Cli>Use commandline (WP-CLI) to purge caches or reset to factory settings.\u003C\u002Fli>\n\u003Cli>Remove id tag from stylesheet link tags, in order to allow Nginx Pagespeed to combine stylesheets.\u003C\u002Fli>\n\u003Cli>Allow purging of other cached items (see Settings > Cache control).\u003C\u002Fli>\n\u003Cli>Inform user of purge status.\u003C\u002Fli>\n\u003Cli>Support for single site and network sites\u003C\u002Fli>\n\u003Cli>Support for WP-CLI\u003C\u002Fli>\n\u003Cli>Support for WPML (including language negotiation type domain)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>When will it purge?\u003C\u002Fh4>\n\u003Cp>This plugin will work with default and custom post types. It will purge on a save, regular update, quick edit update, slug change, delete and undelete. The user is informed with one or more messages.\u003Cbr \u002F>\nThere are a few caveats:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When a user is using the Gutenberg editor, purge messages will not be displayed.\u003C\u002Fli>\n\u003Cli>When the user uses “Quick edit” and “Updates” the post, no messages will be displayed, because there’s no page refresh. Those messages will be shown on the next request. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It is possible to purge with WordPress cronjobs. Adjust the ‘Cronjob settings’ to perform a daily purge of caches.\u003C\u002Fp>\n\u003Cp>You can also purge items manually. Go to the WordPress dashboard and navigate to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Settings > Cache control > purge single item\u003C\u002Fli>\n\u003Cli>Settings > Cache control > purge all caches\u003C\u002Fli>\n\u003Cli>Admin Toolbar > purge all caches\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>File with hosts (JSON):                 File with information about one or more hosts for this WordPress installation. See hosts.json section for more details. \u003C\u002Fli>\n\u003Cli>Pagespeed optimized CSS:                Remove ID tag from all WordPress stylesheet link tags to improve Nginx Pagespeed caching. Will only work on frontend.\u003C\u002Fli>\n\u003Cli>Purge settings default post types:      Select one or more options when purging a default post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.\u003C\u002Fli>\n\u003Cli>Purge settings default custom type(s):  Select one or more options when purging a custom post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Cronjob Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Cronjob purging:                        Enable or disable cronjob purging. \u003C\u002Fli>\n\u003Cli>Cronjob time of each day:               Enter HH:MM in 24 hour notation for cronjob time of day. Will fallback to 00:00 when wrong format is given.\u003C\u002Fli>\n\u003Cli>Purge caches                            Select caches to purge on given cronjob time. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>hosts.json\u003C\u002Fh4>\n\u003Cp>Hosts.json is a JSON file with information about one or more servers for this WordPress installation. Remember that this file must contain information about all servers, including the\u003Cbr \u002F>\none with this plugin. Default path is: wp-content\u002Fuploads\u002Fcacholong-cache-control\u002Fhosts.json.\u003C\u002Fp>\n\u003Cp>Here is an example of a hosts.json file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"servers\":\n    [\n        {\"name\": \"server1\", \"ip\": \"127.0.0.1\", \"pagespeed\": true, \"fastcgi\": false},\n        {\"name\": \"server2\", \"ip\": \"127.0.0.2\", \"pagespeed\": false, \"fastcgi\": true},\n    ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Each line contains information about one server. Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>name (string)\u003Cbr \u002F>\nName of host, something to identify this server.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ip (string)\u003Cbr \u002F>\nIP address of server or full url. Format: scheme:\u002F\u002Fhost:port\u002Fpath\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>pagespeed (bool)\u003Cbr \u002F>\nServer uses Nginx Pagespeed (true) or not (false)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>fastcgi (bool)\u003Cbr \u002F>\nServer user Nginx FastCGI (true) or not (false)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When there is no hosts.json or the path is invalid, this plugin assumes the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"servers\":\n    [\n        {\"name\": \"localhost\", \"ip\": \"127.0.0.1\", \"pagespeed\": true, \"fastcgi\": true}\n    ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>How does it work\u003C\u002Fh4>\n\u003Cp>“Cache control by Cacholong” empties partial or full cache for Nginx Pagespeed and FastCGI cache. WordPress HTTP API is used to make (post) request to\u003Cbr \u002F>\nspecific urls to trigger purges. Based on the http header responses this plugin determines if a purge is successful or not. The user is informed with messages, which are loaded after a purge and page refresh.\u003C\u002Fp>\n\u003Cp>There are several settings to tweak purging, see Settings > Cache control.\u003C\u002Fp>\n\u003Ch4>WP-CLI\u003C\u002Fh4>\n\u003Cp>There are several commands available for the commandline with wp-cli. Commands generate text output which can be suppressed with –quiet. When an error occurs, text will always be displayed.\u003C\u002Fp>\n\u003Ch4>WP-CLI exit codes\u003C\u002Fh4>\n\u003Cp>Exit codes are 0 (no errors) or 1 (generic error).\u003C\u002Fp>\n\u003Ch4>WP-CLI examples\u003C\u002Fh4>\n\u003Cp>Purge command with all arguments:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge [--cache=\u003Ccache>] [--ips=\u003Cips>]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx FastCGI:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=fastcgi\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx Pagespeed:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=pagespeed\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge all caches:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=all\nwp cacholong_cc purge\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx Pagespeed cache for ip address 127.0.0.1 and 127.0.0.2:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=pagespeed --ips=127.0.0.1,127.0.0.2\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge all caches for ip address 127.0.0.1 and 127.0.0.2:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --ips=127.0.0.1,127.0.0.2\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Factory reset options for given site_id or current blog if no site_id is given:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc factory_reset [--site_id=site_id]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Debug\u003C\u002Fh4>\n\u003Cp>Plugin will log basic purge information when WP_DEBUG is true (can be set in wp-config.php). Logs information in file wp-content\u002Fcacholong-cache-control.log.\u003Cbr \u002F>\nPlugin will log wp_remote_request details when CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST is true (can be set in wp-config.php). Logs information in file wp-content\u002Fcacholong-cache-control.log.\u003C\u002Fp>\n","“Cache control by Cacholong” is a cache control plugin for one or more Nginx servers.",500,6645,"2021-07-20T12:01:00.000Z","5.7.15","4.3.1",[20,54,21,55,24],"cache-control","cacholong","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-control-by-cacholong.zip",43,"2025-04-01 00:00:00",{"slug":54,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":13,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":56,"tags":73,"homepage":76,"download_link":77,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"Cache-Control","2.2.5","Dan","https:\u002F\u002Fprofiles.wordpress.org\u002Fgeekysoft\u002F","\u003Cp>Good caching policies is one of performance’s best friends, and it can be your new best friend too. Get friendly with intermediary and browser caches by taking control over your WordPress powered website’s HTTP \u003Ccode>Cache-Control\u003C\u002Fcode> headers.\u003C\u002Fp>\n\u003Cp>This is not a caching plugin in itself, but will enable you to leverage existing standard compliant caching systems better. You can set different policies for different kinds of pages to suite your website’s needs. The Cache-Control for WordPress plugin allows you to set different policies for shared\u002Fintermediary and private caches. The plugin sets some sensible defaults for a medium traffic blog that publishes an update or two per week.\u003C\u002Fp>\n\u003Cp>You can safely set long \u003Ccode>Cache-Control\u003C\u002Fcode> times as the \u003Ccode>max-age\u003C\u002Fcode> values is lowered automatically before a scheduled post is about to be published.\u003C\u002Fp>\n\u003Cp>Private pages (logged in users, the admin interface, etc.) will not be cached.\u003C\u002Fp>\n\u003Cp>The plugin has \u003Ca href=\"https:\u002F\u002Fwww.ctrl.blog\u002Fentry\u002Fwp-cache-control-documentation.html\" rel=\"nofollow ugc\">extensive documentation\u003C\u002Fa>.\u003C\u002Fp>\n","Configurable HTTP Cache-Control response headers for webpages generated by WordPress.",1000,98695,6,"2019-08-30T11:50:00.000Z","5.2.24","4.4.1",[54,21,74,75],"http","performance","https:\u002F\u002Fwww.ctrl.blog\u002Fentry\u002Fwordpress-cache-control-plugin.html","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-control.2.2.5.zip",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":11,"downloaded":86,"rating":28,"num_ratings":28,"last_updated":87,"tested_up_to":88,"requires_at_least":89,"requires_php":56,"tags":90,"homepage":56,"download_link":95,"security_score":96,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"auto-update-cache","Auto Update Cache","1.1","Shiek Md Anwar Hussain Mizan (Sheikh MiZan)","https:\u002F\u002Fprofiles.wordpress.org\u002Fsheikhmizanbd\u002F","\u003Cp>Made CSS\u002FJS file changes but not showing on website? this plugin will help.\u003C\u002Fp>\n\u003Cp>Auto Update Cache allows you to update the version of all CSS and JS files automatically or manually in one click. Show latest changes to the users\u002Fviewers.\u003C\u002Fp>\n\u003Ch4>How it works?\u003C\u002Fh4>\n\u003Cp>By default, WordPress loads assets using query param \\”ver\\” in the URL (e.g., style.css?ver=4.9.6). It allows browsers to cache this files until the WordPress core will not be upgraded to a newer version.\u003C\u002Fp>\n\u003Cp>To prevent caching of CSS and JS files, this plugin adds query param \\”time\\” with beautiful easy to use dashboard panel (e.g., style.css?ver=4.9.6&time=1526905286) to all links, loaded using wp_enqueue_style and wp_enqueue_script functions.\u003C\u002Fp>\n","Update the version of all CSS and JS files. Show the latest changes on the site without asking the client to clear browse",1960,"2024-09-18T09:37:00.000Z","6.6.5","4.0",[79,91,92,93,94],"browser-caching","clear-cache","update-css","update-js","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fauto-update-cache.1.1.zip",92,{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":11,"downloaded":105,"rating":28,"num_ratings":28,"last_updated":106,"tested_up_to":107,"requires_at_least":108,"requires_php":56,"tags":109,"homepage":112,"download_link":113,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"simple-cache-killer","Simple Cache Killer","1.0.2","John Cummings","https:\u002F\u002Fprofiles.wordpress.org\u002Fjcummings1974\u002F","\u003Cp>** For Multisite\u002FNetwork Users **\u003C\u002Fp>\n\u003Cp>I wrote this plugin because of several situations I’ve run in to running a multisite network where I’ll want to include\u003Cbr \u002F>\ncaching for WordPress sites in most cases, but might need to exclude one of the sites on the network from that caching.\u003C\u002Fp>\n\u003Cp>By activating this plugin and checking the different caching options, requests to that sites pages\u002Fposts can be instructed\u003Cbr \u002F>\nnot to cache site content without disrupting the caching strategy in place for other sites.\u003C\u002Fp>\n\u003Cp>** For single site installations **\u003C\u002Fp>\n\u003Cp>This plugin will still be useful for single site installations where the site administrator may not have access to the web server\u003Cbr \u002F>\nto specify the types of HTTP caching headers that are returned on each request.  By allowing you to specify and rewrite the HTTP caching\u003Cbr \u002F>\nheaders at the site level, you’ll no longer need access to the web server in order to make sure visitors are always served fresh\u003Cbr \u002F>\ncontent.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Bug Reports or Feature Requests\u003C\u002Fstrong>\u003Cbr \u002F>\nhttps:\u002F\u002Ftrello.com\u002Fb\u002FzLViVgjx\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Follow me on Twitter\u003C\u002Fstrong>\u003Cbr \u002F>\nhttps:\u002F\u002Ftwitter.com\u002Fjcummings1974\u003C\u002Fp>\n","Allows users to specify that requests to their content not be cached in any way, easily from within the Wordpress admin.",2200,"2014-09-08T16:51:00.000Z","4.0.38","3.0.1",[20,54,21,110,111],"meta-http-equiv","pragma-no-cache","http:\u002F\u002Fwww.jcummings.net","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-cache-killer.zip",{"slug":115,"name":116,"version":117,"author":118,"author_profile":119,"description":120,"short_description":121,"active_installs":122,"downloaded":123,"rating":124,"num_ratings":125,"last_updated":126,"tested_up_to":127,"requires_at_least":128,"requires_php":129,"tags":130,"homepage":133,"download_link":134,"security_score":135,"vuln_count":136,"unpatched_count":28,"last_vuln_date":137,"fetched_at":30},"litespeed-cache","LiteSpeed Cache","7.8","LiteSpeed Technologies","https:\u002F\u002Fprofiles.wordpress.org\u002Flitespeedtech\u002F","\u003Cp>LiteSpeed Cache for WordPress (LSCWP) is an all-in-one site acceleration plugin, featuring an exclusive server-level cache and a collection of optimization features.\u003C\u002Fp>\n\u003Cp>LSCWP supports WordPress Multisite and is compatible with most popular plugins, including WooCommerce, bbPress, and Yoast SEO.\u003C\u002Fp>\n\u003Cp>LiteSpeed Cache for WordPress is compatible with ClassicPress.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>General Features\u003C\u002Fstrong> may be used by anyone with any web server (LiteSpeed, Apache, NGINX, etc.).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>LiteSpeed Exclusive Features\u003C\u002Fstrong> require one of the following: OpenLiteSpeed, commercial LiteSpeed products, LiteSpeed-powered hosting, or QUIC.cloud CDN. \u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002Ffaq\u002F#why-do-the-cache-features-require-a-litespeed-server\" rel=\"nofollow ugc\">Why?\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Plugin Features\u003C\u002Fh3>\n\u003Ch4>General Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Free QUIC.cloud CDN Cache\u003C\u002Fli>\n\u003Cli>Object Cache (Memcached\u002FLSMCD\u002FRedis) Support+\u003C\u002Fli>\n\u003Cli>Image Optimization (Lossless\u002FLossy)\u003C\u002Fli>\n\u003Cli>Minify CSS, JavaScript, and HTML\u003C\u002Fli>\n\u003Cli>Minify inline & external CSS\u002FJS\u003C\u002Fli>\n\u003Cli>Combine CSS\u002FJS\u003C\u002Fli>\n\u003Cli>Automatically generate Critical CSS\u003C\u002Fli>\n\u003Cli>Lazy-load images\u002Fiframes\u003C\u002Fli>\n\u003Cli>Responsive Image Placeholders\u003C\u002Fli>\n\u003Cli>Multiple CDN Support+\u003C\u002Fli>\n\u003Cli>Load CSS Asynchronously\u003C\u002Fli>\n\u003Cli>Defer\u002Fdelay JS loading\u003C\u002Fli>\n\u003Cli>Browser Cache Support+\u003C\u002Fli>\n\u003Cli>Database Cleaner and Optimizer\u003C\u002Fli>\n\u003Cli>PageSpeed score (including Core Web Vitals) optimization\u003C\u002Fli>\n\u003Cli>OPcode Cache Support+\u003C\u002Fli>\n\u003Cli>HTTP\u002F2 Push for CSS\u002FJS (on web servers that support it)\u003C\u002Fli>\n\u003Cli>DNS Prefetch\u003C\u002Fli>\n\u003Cli>Cloudflare API\u003C\u002Fli>\n\u003Cli>Single Site and Multisite (Network) support\u003C\u002Fli>\n\u003Cli>Import\u002FExport settings\u003C\u002Fli>\n\u003Cli>Attractive, easy-to-understand interface\u003C\u002Fli>\n\u003Cli>AVIF\u002FWebP image format support\u003C\u002Fli>\n\u003Cli>Heartbeat control\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>+ This service is not provided by the LSCache plugin, nor is it guaranteed to be installed by your service provider. However, the plugin is compatible with the service if it is in use on your site.\u003C\u002Fp>\n\u003Ch4>LiteSpeed Exclusive Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Automatic page caching to greatly improve site performance\u003C\u002Fli>\n\u003Cli>Automatic purge of related pages based on certain events\u003C\u002Fli>\n\u003Cli>Private cache for logged-in users\u003C\u002Fli>\n\u003Cli>Caching of WordPress REST API calls\u003C\u002Fli>\n\u003Cli>Separate caching of desktop and mobile views\u003C\u002Fli>\n\u003Cli>Ability to schedule purge for specified URLs\u003C\u002Fli>\n\u003Cli>WooCommerce and bbPress support\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002Fcli\u002F\" rel=\"nofollow ugc\">WordPress CLI\u003C\u002Fa> commands\u003C\u002Fli>\n\u003Cli>API system for easy cache integration\u003C\u002Fli>\n\u003Cli>Exclude from cache by URI, Category, Tag, Cookie, User Agent\u003C\u002Fli>\n\u003Cli>Smart preload crawler with support for SEO-friendly sitemap\u003C\u002Fli>\n\u003Cli>Multiple crawlers for cache varies\u003C\u002Fli>\n\u003Cli>HTTP\u002F2 support\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.litespeedtech.com\u002Fhttp3-faq\" rel=\"nofollow ugc\">HTTP\u002F3 & QUIC\u003C\u002Fa> support\u003C\u002Fli>\n\u003Cli>ESI (Edge Side Includes) support*\u003C\u002Fli>\n\u003Cli>Widgets and Shortcodes as ESI blocks* (requires Classic Widgets plugin for WP 5.8+)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>* Feature not available in OpenLiteSpeed\u003C\u002Fp>\n\u003Ch3>LSCWP Resources\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Flitespeedtech.com\u002Fslack\" rel=\"nofollow ugc\">Join our Slack community\u003C\u002Fa> to connect with other LiteSpeed users.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Flitespeed-cache\u002F\" rel=\"ugc\">Ask a question on our support forum\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002F\" rel=\"nofollow ugc\">View detailed documentation\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fblog.litespeedtech.com\u002Ftag\u002Fwordpress\u002F\" rel=\"nofollow ugc\">Read about LSCWP and WordPress on our blog\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Flitespeed-cache\u002F\" rel=\"nofollow ugc\">Help translate LSCWP\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flitespeedtech\u002Flscache_wp\" rel=\"nofollow ugc\">Contribute to the LSCWP GitHub repo\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Third Party Compatibility\u003C\u002Fh3>\n\u003Cp>The vast majority of plugins and themes are compatible with LSCache. \u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002Fapi\u002F\" rel=\"nofollow ugc\">Our API\u003C\u002Fa> is available for those that are not. Use the API to customize smart purging, customize cache rules, create cache varies, and make WP nonce cacheable, among other things.\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>This plugin includes some suggested text that you can add to your site’s Privacy Policy via the Guide in the WordPress Privacy settings.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>For your own information:\u003C\u002Fstrong> LiteSpeed Cache for WordPress potentially stores a duplicate copy of every web page on display on your site. The pages are stored locally on the system where LiteSpeed server software is installed and are not transferred to or accessed by LiteSpeed employees in any way, except as necessary in providing routine technical support if you request it. All cache files are temporary, and may easily be purged before their natural expiration, if necessary, via a Purge All command. It is up to individual site administrators to come up with their own cache expiration rules.\u003C\u002Fp>\n\u003Cp>In addition to caching, our WordPress plugin has online features provided by QUIC.cloud for Image Optimization and Page Optimization services. When one of these optimizations is requested, data is transmitted to a remote QUIC.cloud server, processed, and then transmitted back for use on your site. QUIC.cloud keeps copies of that data for up to 7 days and then permanently deletes it. Similarly, the WordPress plugin has a Reporting feature whereby a site owner can transmit an environment report to LiteSpeed so that we may better provide technical support. None of these features collects any visitor data. Only server and site data are involved.\u003C\u002Fp>\n\u003Cp>QUIC.cloud CDN, if enabled, uses LSCache technology to access your site, and serve your content from remote global nodes. Your data is not accessed by QUIC.cloud employees in any way, except as necessary in providing maintenance or technical support.\u003C\u002Fp>\n\u003Cp>Please see the \u003Ca href=\"https:\u002F\u002Fquic.cloud\u002Fprivacy-policy\u002F\" rel=\"nofollow ugc\">QUIC.cloud Privacy Policy\u003C\u002Fa> for our complete Privacy\u002FGDPR statement.\u003C\u002Fp>\n","All-in-one unbeatable acceleration & PageSpeed improvement: caching, image\u002FCSS\u002FJS optimization...",7000000,126174082,96,2718,"2026-03-03T18:24:00.000Z","6.9.4","5.3","7.2",[21,131,24,75,132],"optimize","seo","https:\u002F\u002Fwww.litespeedtech.com\u002Fproducts\u002Fcache-plugins\u002Fwordpress-acceleration","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flitespeed-cache.7.8.zip",82,18,"2025-10-28 00:00:00",{"attackSurface":139,"codeSignals":191,"taintFlows":221,"riskAssessment":239,"analyzedAt":246},{"hooks":140,"ajaxHandlers":187,"restRoutes":188,"shortcodes":189,"cronEvents":190,"entryPointCount":28,"unprotectedCount":28},[141,147,151,155,159,163,167,171,175,179,183],{"type":142,"name":143,"callback":144,"file":145,"line":146},"action","admin_init","wao_io_cc_settings_init","wao-io-cache-control.php",66,{"type":142,"name":148,"callback":149,"file":145,"line":150},"admin_menu","wao_io_cc_menu_setup",199,{"type":142,"name":152,"callback":153,"file":145,"line":154},"admin_post_clear_cache","wao_io_api_clear_cache_manual",200,{"type":142,"name":156,"callback":157,"file":145,"line":158},"admin_notices","wao_io_activation_notice",204,{"type":142,"name":160,"callback":161,"priority":11,"file":145,"line":162},"publish_post","wao_io_cc_contentchange_publish_post",219,{"type":142,"name":164,"callback":165,"priority":11,"file":145,"line":166},"publish_page","wao_io_cc_contentchange_publish_page",220,{"type":142,"name":168,"callback":169,"priority":11,"file":145,"line":170},"after_switch_theme","wao_io_cc_contentchange_switch_theme",221,{"type":142,"name":172,"callback":173,"priority":11,"file":145,"line":174},"customize_save_after","wao_io_cc_contentchange_customize_theme",222,{"type":142,"name":176,"callback":177,"priority":11,"file":145,"line":178},"update_theme_complete_actions","wao_io_cc_contentchange_update_theme",223,{"type":142,"name":180,"callback":181,"priority":11,"file":145,"line":182},"upgrader_process_complete","wao_io_cc_contentchange_upgrader_complete",224,{"type":142,"name":184,"callback":185,"file":145,"line":186},"plugins_loaded","wao_io_cc_load_plugin_textdomain",256,[],[],[],[],{"dangerousFunctions":192,"sqlUsage":193,"outputEscaping":195,"fileOperations":28,"externalRequests":14,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":220},[],{"prepared":28,"raw":28,"locations":194},[],{"escaped":196,"rawEcho":11,"locations":197},5,[198,202,204,205,207,209,211,213,215,218],{"file":199,"line":200,"context":201},"cache-control.php",65,"raw output",{"file":199,"line":203,"context":201},69,{"file":199,"line":13,"context":201},{"file":199,"line":206,"context":201},101,{"file":199,"line":208,"context":201},104,{"file":199,"line":210,"context":201},107,{"file":199,"line":212,"context":201},110,{"file":199,"line":214,"context":201},113,{"file":216,"line":217,"context":201},"includes\\header.php",22,{"file":145,"line":219,"context":201},71,[],[222],{"entryPoint":223,"graph":224,"unsanitizedCount":14,"severity":238},"\u003Ccache-control> (cache-control.php:0)",{"nodes":225,"edges":235},[226,230],{"id":227,"type":228,"label":229,"file":199,"line":214},"n0","source","$_SERVER['REQUEST_TIME']",{"id":231,"type":232,"label":233,"file":199,"line":214,"wp_function":234},"n1","sink","echo() [XSS]","echo",[236],{"from":227,"to":231,"sanitized":237},false,"low",{"summary":240,"deductions":241},"The \"wao-io-cache-control\" v1.0.0 plugin exhibits a generally good security posture due to a lack of identified critical vulnerabilities and a complete absence of known CVEs. The code also demonstrates responsible practices by utilizing prepared statements for all SQL queries and not performing any file operations or external HTTP requests without apparent safeguards. The presence of only one external HTTP request is noted, and while not explicitly flagged as insecure, it warrants careful monitoring.  The primary concern arises from the taint analysis, which revealed one flow with an unsanitized path. Although this did not reach a critical or high severity, it indicates a potential weakness that could be exploited under specific conditions. Furthermore, the lack of output escaping for a significant portion (67%) of identified outputs is a notable risk, potentially exposing the application to Cross-Site Scripting (XSS) vulnerabilities if user-controlled data is not properly handled before display.\n\nWhile the plugin has no recorded vulnerability history, suggesting a stable and well-maintained codebase thus far, the identified taint flow and insufficient output escaping are areas that require immediate attention. The absence of any reported vulnerabilities is a positive indicator, but it does not negate the risks identified through static and taint analysis. Future development should prioritize addressing the unsanitized path and ensuring all output is properly escaped to maintain a robust security profile.  The plugin's strengths lie in its SQL handling and lack of known exploits, but its weaknesses in output sanitization and the presence of an unsanitized path need to be rectified.",[242,244],{"reason":243,"points":11},"Unsanitized path in taint flow",{"reason":245,"points":69},"Insufficient output escaping","2026-03-17T00:55:57.159Z",{"wat":248,"direct":257},{"assetPaths":249,"generatorPatterns":252,"scriptPaths":253,"versionParams":254},[250,251],"\u002Fwp-content\u002Fplugins\u002Fwao-io-cache-control\u002Fadmin\u002Fcss\u002Fmain.css","\u002Fwp-content\u002Fplugins\u002Fwao-io-cache-control\u002Fadmin\u002Fjs\u002Fmain.js",[],[251],[255,256],"wao-io-cache-control\u002Fadmin\u002Fcss\u002Fmain.css?ver=","wao-io-cache-control\u002Fadmin\u002Fjs\u002Fmain.js?ver=",{"cssClasses":258,"htmlComments":260,"htmlAttributes":263,"restEndpoints":265,"jsGlobals":266,"shortcodeOutput":268},[259],"wao-io-cache-control-wrapper",[261,262],"\u003C!-- wao.io Cache Control by Avenga Germany GmbH -->","\u003C!-- If you do not have an API key yet, please contact wao.io support! -->",[264],"data-wao-io-cache-control-nonce",[],[267],"wao_io_cc_ajax_object",[]]