hakre

<p>Better HTTP Redirects makes your Blog’s redirects to play more nicely the HTTP standards. Dual Mode Plugin, can be used as a standard Plugin or as a Must-Use Plugin.</p>
<h4>Features</h4>
<ul>
<li>Provide Hypertext Fragments on redirects where applicable.</li>
<li>Compatible with <em>any</em> current usage of the wp_redirect() API function.</li>
<li>Prevent unnecessary redirect loops on UTF-8 based sites.</li>
<li>Improved user and robot (search engines etc.) experience for your website.</li>
<li>No need for you to wait until core code get’s fixed – if ever!</li>
<li>Helps you debugging redirect related issues with it’s unique <a href="http://hakre.wordpress.com/2011/03/20/how-to-debug-redirect-problems-in-wordpress" rel="nofollow ugc">Redirect Debug Mode</a>.</li>
<li>Free</li>
</ul>
<h3>TODO</h3>
<ul>
<li>Verify that the plugin is stricly preventing redirects that redirect to the same URI (see RFC 2616 section 3.2.3).</li>
</ul>
<h3>Integration</h3>
<p>“Better HTTP Redirects” works out of the box but for a better integration you can make use of the following:</p>
<ul>
<li>Hook <strong>redirect_hypertext</strong> <code>$hypertext = apply_filters('redirect_hypertext', $hypertext, $location, $status);</code></li>
</ul>
<h3>Document Scope</h3>
<p>This file readme.txt has been created in the intention to provide data to be displayed <a href="https://wordpress.org/extend/plugins/better-http-redirects/" rel="ugc">on the wordpress.org plugin repository website</a>. As always, for anything concrete and precise, refer to <a href="https://plugins.trac.wordpress.org/browser/better-http-redirects/trunk/better-http-redirects.php" rel="nofollow ugc">the plugin sourcecode itself</a>, it ships with <a href="http://en.wikipedia.org/wiki/PHPDoc" rel="nofollow ugc">phpdoc style comments</a>.</p>


Better HTTP Redirects

Better HTTP Redirects makes your Blog's redirects to play more nicely the HTTP standards.

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.

Better HTTP Redirects vs Remove HTTP: Fix Mixed Content Warning