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.

JS Morisset

<p><strong>A simple, safe, and reliable way to force HTTP URLs to HTTPS dynamically:</strong></p>
<p>No setup required – simply activate the plugin to force HTTP URLs to HTTPS.</p>
<p>There are no plugin settings to adjust, and no changes are made to your WordPress configuration.</p>
<p><strong>SIGNIFICANTLY FASTER than other popular plugins of this type:</strong></p>
<p>Other well known plugins use <a href="https://secure.php.net/manual/en/function.ob-start.php" rel="nofollow ugc">PHP’s output buffer</a> to search & replace URLs in the rendered HTML, which is a technique that is error prone and <em>negatively affects caching performance</em> (as changes are not cached).</p>
<p>This plugin uses standard WordPress filters instead of PHP’s output buffer for maximum reliability, performance, caching compatibility, and uses 301 permanent redirects for best SEO results (<a href="https://en.wikipedia.org/wiki/HTTP_301" rel="nofollow ugc">301 redirects are considered best for SEO when moving from HTTP to HTTPS</a>).</p>
<p><strong>Supports advanced proxy / load-balancing HTTP headers:</strong></p>
<ul>
<li><code>X-Forwarded-Proto</code> (aka <code>HTTP_X_FORWARDED_PROTO</code> server value)</li>
<li><code>X-Forwarded-Ssl</code> (aka <code>HTTP_X_FORWARDED_SSL</code> server value)</li>
</ul>
<p>See <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto" rel="nofollow ugc">Web technology for developers > HTTP > HTTP headers > X-Forwarded-Proto</a> for more details.</p>
<h4>Plugin Requirements</h4>
<p>Your web server must already be configured with an SSL certificate and able to handle HTTPS connections. 😉</p>


JSM Force HTTP to HTTPS / SSL – No Setup, Fast and Reliable

No setup required - simply activate to force HTTP URLs to HTTPS using native WordPress filters and permanent redirects for best SEO.

Remove HTTP: Fix Mixed Content Warning vs JSM Force HTTP to HTTPS / SSL – No Setup, Fast and Reliable