shawfactor

Asitha

<p>This plugin send the proper headers for full ssl security. For more information on what this is and why it is important visit: http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security</p>
<p>The options are preset to enable browsers to preload the HSTS directive but can be overwritten by filters which are clearly documented in the code.</p>
<p><strong>Did you find this plugin helpful? Please consider <a href="https://wordpress.org/support/view/plugin-reviews/lh-hsts" rel="ugc">writing a review</a>.</strong></p>
<h3>To update the max-age settings, add the following code to your functions.php</h3>
<pre><code>add_filter('lh_hsts_max_age', 'modify_ls_hsts_max_age_func');

function modify_ls_hsts_max_age_func( $max_age ){
    return false;
}
    `

<h3>To update the subdomain settings, add the following code to your functions.php</h3>

</code></pre>
<p>add_filter(‘lh_hsts_subdomain’, ‘modify_ls_hsts_subdomain_func’);</p>
<p>function modify_ls_hsts_subdomain_func( $subdomain ){<br />
    return false;<br />
}<br />
    `</p>
<h3>To update the preload setting, add the following code to your functions.php</h3>
<pre><code>add_filter('lh_hsts_preload', 'modify_ls_hsts_preload_func');

function modify_ls_hsts_preload_func( $preload ){
    return false;
}
    `

<h3>To update the redirect setting, add the following code to your functions.php</h3>

</code></pre>
<p>add_filter(‘lh_hsts_redirect’, ‘modify_ls_hsts_redirect_func’);</p>
<p>function modify_ls_hsts_redirect_func( $redirect ){<br />
    return false;<br />
}<br />
    `</p>


LH HSTS

Using with WordPress 4.9.4 and can verify the correct header is being set. Thanks!

Works Splendidly

Not only does this not work - YOU CANNOT DISABLE OR REMOVE HSTS after this plugin!

I can't access my website anymore, because this 'author' made it impossible to remove or disable hsts - I disabled and removed the plugin, cleared cache, rebooted the server - HSTS is still on!!!!!!

completely broken

HSTS is HTTP Strict Transport Security, a means to enforce using SSL even if the user accesses the site through HTTP and not HTTPS.

Blucube

<p>If your site has an SSL certificate you might find that you can access the site via both SSL (https) and non-SSL (http) URLs. This is a bad idea for security, and for SEO, as it can look like duplicate content on different URLs.</p>
<p>The answer to this is to redirect requests to non-SSL (http) URLs over to their SSL (https) equivalents using something called a 301 redirect. This tells the client (and search engines) that the resource they are looking for should always be accessed over SSL.  This plugin offers two methods to achieve this:</p>
<ul>
<li>By intercepting WordPress pages at header time, and if they are not already being requested over HTTPS sending a 301 redirect header, or</li>
<li>By adding mod_rewrite rules in the .htaccess file to redirect all requests to their HTTPS equivalents using 301 redirects.</li>
</ul>
<p>Optionally, this plugin can also set <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security" rel="nofollow ugc">HSTS</a> headers for you, and make sure that all requests use the same hostname (i.e. fixing the issue where many sites can be accessed using both www. and non-www. URLs).</p>


Simple SSL Redirects

Lightweight plugin to ensure access via SSL/HTTPS. Uses 301 (permanent) redirects for SEO benefits. Optionally sets HSTS and forces canonical domain.

LH HSTS vs Simple SSL Redirects