Ian Dunn

Redirects all HTTPS traffic to HTTP, except for specific exceptions. You might want to do this to minimize the number of times users would see an error if you don’t have a valid SSL certificate setup, or if you want to make sure that the delay SSL adds is only experienced when necessary.

Force non-SSL

Redirects all HTTPS traffic to HTTP, except for specific exceptions

florianluce

With WP htaccess Optimize, you can easily optimize the performance of your site by configuring your htaccess in bit clicks
optimisation available:
<ul>
<li>Time zone selection</li>
<li>Prevents indexing of folders without index.php</li>
<li>Disable the server signature</li>
<li>Block Sensitive Files</li>
<li>Protect WP-includes</li>
<li>Protect author link</li>
<li>Block author scans</li>
<li>Enabling the tracking of symbolic links</li>
<li>Comment spam</li>
<li>Protection against file injections</li>
<li>Various protections ( XSS, clickjacking and MIME-Type sniffing )</li>
<li>Disable the hotlinking of your pictures</li>
<li>Redirect without WWW</li>
<li>Redirect http to HTTPS</li>
<li>Caching files in the browser</li>
<li>Disabled headers ETags</li>
<li>Compress static files</li>
</ul>

WP htaccess Optimize (beta)

simply configure your htaccess to optimize your site!

Force non-SSL vs WP htaccess Optimize (beta)