andresmesi

Mesi Cache converts your WordPress site into a fully static HTML version served 
directly by Apache. Once a page is cached, it is delivered instantly without 
executing PHP or querying MySQL.
This design removes the need for PHP-FPM and database access on every visit, 
reducing server load to almost zero. The result is a pure static experience with 
instant page delivery and total control over your server resources.
Mesi Cache is minimalist, open, and transparent. It integrates cleanly with 
 .htaccess, uses no cron jobs, and requires no external services.
What it does 
* Creates static HTML files of posts, pages, categories and authors. 
* Serves files directly from disk, bypassing PHP and MySQL completely. 
* Invalidates relevant cache files when new content is published. 
* Allows manual cache generation and cleaning from the admin panel. 
* Works in root and subdirectory installations. 
* 100% local — no APIs, no remote calls, no external dependencies.
What it does not do 
* No CSS or JS minification. 
* No CDN integration (can be added manually). 
* No object or fragment caching. 
* No user/session-aware pages or dynamic content. 
* Does not serve cached content to logged-in users.
Mesi Cache focuses purely on static HTML delivery for public visitors. 
When cached, pages are served as plain files — no PHP or database code executes.
The plugin code is open, commented, and easy to extend. 
Developers can add features like preloading or CDN hooks using ChatGPT, Gemini, 
or manual edits.
<h3>License</h3>
This plugin is licensed under GPLv2 or later. 
You are free to use, modify, and redistribute it.

Mesi Cache

Ultra-light static HTML caching system for WordPress.

Faison

<a href="http://faisonz.com/" title="Faison Zutavern's Personal Blog" rel="nofollow ugc">Faison Zutavern</a>, <a href="https://profiles.wordpress.org/jvalcq" title="Jon's WordPress.org Profile" rel="nofollow ugc">Jon Valcq</a>, and <a href="https://profiles.wordpress.org/emmaee" title="Emma's WordPress.org profile" rel="nofollow ugc">Emma Edgar</a>, from <a href="http://www.orionweb.net/" title="Milwaukee Area Web Developers" rel="nofollow ugc">Orion Group LLC</a>, bring superior Brute Force Attack protection to WordPress with their new plugin, Project Force Field. By tracking failed login attempts and taking advantage of Apache’s mod_rewrite module, Project Force Field stops Brute Force Attacks from bogging down your sites and servers.
Special thanks to <a href="http://www.aykcreative.com/" title="Ayk Creative | Graphic Support for your Projects" rel="nofollow ugc">Chris Aykroid</a> for the plugin banner 😀
<h4>Contributing</h4>
If you would like to contribute or fork Project Force Field, we currently have a repo on Bitbucket. You can <a href="https://bitbucket.org/oriongroup/project-force-field/" rel="nofollow ugc">find it here</a>
<h4>Features!</h4>
<ul>
<li>Sends a 403 error code to anyone visiting /wp-login.php – All brute force attacks we’ve seen target /wp-login.php. By responding with a 403 error, your WordPress files aren’t loaded, the Database isn’t queried, and the attacker doesn’t figure out your password.</li>
<li>Changes the default login url – While a so-called hacker is being deflected by your new Force Field, you will log in with ease at /wp-admin/. When you do that, WordPress will redirect you to the new, proper login url.</li>
<li>Automatically changes the login when a Brute Force Attack is detected – When too many login failures occur within a minute, Project Force Field shifts polarity! The new login you previously used now responds with a 403 error, and a large random number is now used as your login url! After some time, the login will return back to normal.</li>
<li>Unlimited polarity shifts – If a Brute Force Attacker gets smart and writes a script to check for the new login url, Project Force Field will continue to detect the attack and change the login.</li>
<li>Define the login yourself – By defining <code>OGFF_LOGIN</code> in your wp-config.php, you can set the login to be almost anything you want.</li>
<li>Stops WordPress User Enumeration Exploit – Many brute force attacks use the WordPress User Enumeration exploit to easily figure out valid usernames. We stop that to protect your site, and respond with a 403 to save your server.</li>
</ul>
<h4>Future Features!</h4>
<ul>
<li>Multisite Support – It’s not there yet, that’s pretty lame, so I’m going to fix that before anything else!</li>
<li>Adjust the login failure threshold – Currently, Project Force Field assumes a brute force is underway when there have been 30 login failures within a minute. This might not be ideal for large websites, so we want to let you increase that amount to 300 if needed.</li>
<li>Add optional email notification for brute force events – If you want to know when your website is under attack, we want to let you know. In a near future version, we will let you add email addresses to be notified of brute force attacks, and any other important related events that we add in the future.</li>
<li>Add last resort .htaccess password lockdown – If a so-called hacker writes a script that continues to learn the new login url, Project Force Field won’t help much. In an upcoming version, we will check to see how many times the login url was changed, determine if the Brute Force Attack is smart, and lockdown the login with an .htaccess password.</li>
</ul>

Project Force Field

Save your WordPress sites and servers from certain death during brute force attacks with Project Force Field by Orion Group!

Mesi Cache vs Project Force Field