Wordpress email obfuscator update#

Enable Email Obfuscation On Contact Page Only So in case anything happens with your WordPress site, at least your most important pages will still be up. wp-content/uploads*Īlways Online keeps your most important pages online if your server goes down and can be turned on for your most important pages (homepage, contact, terms of service, etc). In this page rule (and the next one), browser cache TTL is set to a day.

Wordpress email obfuscator update#

If you need to update certain files/directories before a month, you can purge the individual files in Cloudflare. Since items in your WordPress uploads file don’t change frequently, you don’t have to cache them as often which saves bandwidth by setting Edge Cache TTL to a month. xmlrpc.php*ĭisabling trackbacks/pingbacks in the WordPress Discussion settings also provides an additional layer of security against these attacks (and can saves server resources as well). This assumes you don’t need the Rest API and I would test your website after adding this rule, since some websites/plugins may need it. *preview=true*Īttacks on XMLRPC are common, so this will forward requests from your xmlrpc.php file to any URL you choose (you can just use your homepage). This bypasses Cloudflare’s cache on preview pages since you want to make sure you’re seeing the correct version. It also disables Cloudflare apps and performance features in the admin (minify, Rocket Loader, Mirage, Polish) since these should only used to speed up the frontend. This sets the security level to high and bypasses Cloudflare’s cache since the wp-admin area shouldn’t be cached. Your WordPress Admin should have a few settings which are combined into 1 page rule. Secure The WordPress Admin And Bypass Cache However, it shouldn’t be used as an SSL replacement.Ģ. Opportunistic encyption allows visitors to access your site over an encrypted TLS channel. If your WordPress site is not using SSL, you can use the same pattern only with opportunistic encryption (instead of Always Use HTTPS). This saves you from having to use one of your 3 page rules. Alternatively, you can enable this in your Cloudflare dashboard under SSL/TLS → Edge Certificates → Always Use HTTPS. The asterisks make sure no matter which variation is entered, all visits through HTTP will be redirected to HTTPS. The pattern is recommended in Cloudflare’s page rules YouTube tutorial. The first page rule forces visitors to connect with HTTPS. eCommerce Sites And Dynamic Content Using AJAX.Enable Email Obfuscation On Contact Page Only.Secure The WordPress Admin And Bypass Cache.