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.

PressPage Entertainment Inc

<p>This plugin was developed to solve a redirection issue when navigating from a secured checkout page back to<br />
a non-secured page (or page that you need to have as non-secured—possibly because of non-secured<br />
external links, etc.)</p>
<p>For example, a user comes to your wordpress e-commerce site, locates an item, then navigates to your<br />
secured checkout page. Now the customer, realizes there is something else they need, and instead of clicking<br />
a Continue Shopping link, then click a top category link. Since the customer is in a secured session, wordpress<br />
put the secured protocol on all the links including that category. Now the customer navigates to that<br />
category, but they are still in a secured page session. Now this category page is displaying improperly because<br />
of some external links that did not translate properly into the secured session. Customer is now upset, thinking<br />
that the site design demonstrates the level of incompetence of the shop owner and questions the shop owner’s<br />
integrity to fulfill the customer’s order, so the customer in a behavior of discuss, rapidly leaves the<br />
shop owner’s site and that customer becomes a non-customer!</p>
<p>This plugin resolves this issue by redirecting all non specified checkout (and other non-secured pages)<br />
back to a non-secured page counterpart.</p>
<h3>Credits</h3>
<p>We make honorable mention to anyone who helps make Mavis HTTPS to HTTP Redirect a better plugin!</p>
<h3>Contact</h3>
<p>Support is provided at https://github.com/pingleware/mavis-https-to-http-redirect/issues. You will require a free account on github.com</p>
<p>Please contact presspage.entertainment@gmail.com or visit the above forum with questions, comments, or requests.</p>


Mavis HTTPS to HTTP Redirection

Provides page redirection back to non-secured pages (https: to http:)

Better HTTP Redirects vs Mavis HTTPS to HTTP Redirection