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.

Simon Waters

<p>TLS is growing in complexity. Server Name Indication (SNI) now means HTTPS sites may be on shared IP addresses, or otherwise restricted. For these servers it is handy to be able to set desired HTTP headers without access to the web servers configuration or using .htaccess file.</p>
<p>This plug-in exposes controls for:</p>
<ul>
<li>HSTS (Strict-Transport-Security)</li>
<li>HPKP (Public-Key-Pins)</li>
<li>Disabling content sniffing (X-Content-Type-Options)</li>
<li>XSS protection (X-XSS-Protection)</li>
<li>Clickjacking mitigation (X-Frame-Options in main site)</li>
<li>Expect-CT</li>
</ul>
<p>HSTS is used to ensure that future connections to a website always use TLS, and disallowing bypass of certificate warnings for the site.</p>
<p>HPKP is used if you don’t want to rely solely on the Certificate Authority trust model for certificate issuance.</p>
<p>Disabling content sniffing is mostly of interest for sites that allow users to upload files of specific types, but that browsers might be silly enough to interpret of some other type, thus allowing unexpected attacks.</p>
<p>XSS protection re-enables XSS protection for the site, if the user has disabled it previously, and sets the “block” option so that attacks are not silently ignored.</p>
<p>Clickjacking protection is usually only relevant when someone is logged in but users requested it, presumably they have rich content outside of WordPress authentication they wish to protect.</p>
<p>Expect-CT is used to ensure Certificate Transparency is configured correctly.</p>


Security Headers

Plug-in to ease the setting of TLS headers for HSTS and similar

LH HSTS vs Security Headers