Fact Maven

Ethan O'Sullivan

<blockquote>
<p><strong>Remove HTTP</strong> is a plugin that automatically scans and removes both <code>http:</code> and <code>https:</code> protocols from all links. This helps resolve websites that are having “<a href="https://wordpress.org/plugins/remove-http/faq/" rel="ugc">mixed content warnings</a>” which is when the website has assets (images, JavaScript, and CSS) loading both HTTP and HTTPS.</p>
</blockquote>
<p>No changes to the links are made in the database. Simply install and activate the plugin and the changes will be immediate. Links that have <code>http://</code> or <code>https://</code> will only have <code>//</code>, making them protocol relative URLs. Below is a before and after example.</p>
<h4>Before</h4>
<pre><code><link rel='stylesheet' href='https://example.com/style.css' type='text/css' />
<script type='text/javascript' src='http://example.com/script.js'></script>
<a href="https://example.com" title="Example">Example</a>
<img src="http://example.com/image.jpg" width="150" height="50" />
</code></pre>
<h4>After</h4>
<pre><code><link rel='stylesheet' href='//example.com/style.css' type='text/css' />
<script type='text/javascript' src='//example.com/script.js'></script>
<a href="//example.com" title="Example">Example</a>
<img src="//example.com/image.jpg" width="150" height="50" />
</code></pre>
<h4>Switch to Relative URLs</h4>
<p>There is an option (under the <em>General</em> settings) to change internal links to relative URLs.</p>
<h4>Contribute on GitHub</h4>
<p>Want to help improve this plugin? Head over to our <a href="https://github.com/factmaven/remove-http/" rel="nofollow ugc">GitHub page</a>.</p>


Remove HTTP: Fix Mixed Content Warning

Fixes all mixed content warnings. Removes both HTTP and HTTPS protocols from all links from the front-end and back-end.

webaware

<p>Clean up your WordPress website’s HTTPS insecure content and mixed content warnings. Installing the SSL Insecure Content Fixer plugin will solve most insecure content warnings with little or no effort. The remainder can be diagnosed with a few simple tools.</p>
<p>When you install SSL Insecure Content Fixer, its default settings are activated and it will automatically perform some basic fixes on your website using the Simple fix level. You can select more comprehensive fix levels as needed by your website.</p>
<p>WordPress Multisite gets a network settings page. This can be used to set default settings for all sites within a network, so that network administrators only need to specify settings on sites that have requirements differing from the network defaults.</p>
<p>See the <a href="https://ssl.webaware.net.au/" rel="nofollow ugc">SSL Insecure Content Fixer website</a> for more details.</p>
<h3>Translations</h3>
<p>Many thanks to the generous efforts of our translators:</p>
<ul>
<li>Bulgarian (bg_BG) — <a href="https://translate.wordpress.org/locale/bg/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Bulgarian translation team</a></li>
<li>Chinese simplified (zh_CN) — <a href="https://translate.wordpress.org/locale/zh-cn/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Chinese translation team</a></li>
<li>English (en_CA) — <a href="https://translate.wordpress.org/locale/en-ca/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the English (Canadian) translation team</a></li>
<li>English (en_GB) — <a href="https://translate.wordpress.org/locale/en-gb/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the English (British) translation team</a></li>
<li>English (en_ZA) — <a href="https://translate.wordpress.org/locale/en-za/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the English (South African) translation team</a></li>
<li>Dutch (nl_NL) — <a href="https://translate.wordpress.org/locale/nl/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Dutch translation team</a></li>
<li>German (de_DE) — <a href="https://translate.wordpress.org/locale/de/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the German translation team</a></li>
<li>French (fr_FR) — <a href="https://translate.wordpress.org/locale/fr/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the French translation team</a></li>
<li>Italian (it_IT) — <a href="https://translate.wordpress.org/locale/it/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Italian translation team</a></li>
<li>Japanese (ja) — <a href="https://translate.wordpress.org/locale/ja/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Japanese translation team</a></li>
<li>Russian (ru_RU) — <a href="https://translate.wordpress.org/locale/ru/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Russian translation team</a></li>
<li>Spanish (es_ES) — <a href="https://translate.wordpress.org/locale/es/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Spanish translation team</a></li>
</ul>
<p>If you’d like to help out by translating this plugin, please <a href="https://translate.wordpress.org/projects/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">sign up for an account and dig in</a>.</p>
<h3>Privacy</h3>
<p>SSL Insecure Content Fixer does not collect any personally identifying information, and does not set any cookies.</p>


SSL Insecure Content Fixer

This plugin is very helpful in making sure that a WordPress site will load fully in HTTPS.

This Plugin Does EXACTLY as it says - GREAT WORK!

Clean up WordPress website HTTPS insecure content

Remove HTTP: Fix Mixed Content Warning vs SSL Insecure Content Fixer