Mickey Kay

MIGHTYminnow

<p>Use the simple <code>[http-url]</code> shortcode to convert any URL to either HTTP or HTTPS.</p>
<h4>The Shortcode</h4>
<pre><code>[http-url]
</code></pre>
<p>By default the <code>[http-url]</code> shortcode will output the URL of the current post converted to HTTP. Note: must be used within the loop.</p>
<h4>Shortcode Attributes</h4>
<p><strong><code>url</code></strong> – manually specify the URL to be converted (can be used outside the loop):<br />
    [http-url url=”https://mysite.com”]</p>
<p><strong><code>to_https</code></strong> – convert URL to HTTPS, instead of to HTTP:<br />
    [http-url to_https=”true”]</p>
<h4>PHP Usage</h4>
<p>HTTP URLs also provides two functions that can be used in your php:<br />
    hu_get_http_url( $url ); // Returns URL converted to HTTP<br />
    hu_get_https_url( $url ); // Returns URL converted to HTTPS</p>
<h4>Why Use This Plugin?</h4>
<p>The most common case for using this plugin is in conjunction with social media sharing/commenting plugins, in which data is tied to a specific URL. On sites that are visible via both HTTP and HTTPS, this means that two different sets of differing data are created for every page. HTTP URLs provides a handy solution to this common problem. <a href="http://www.mightyminnow.com/2014/05/how-to-make-social-media-shares-counts-and-comments-work-across-http-and-https/" rel="nofollow ugc">Learn More →</a></p>


HTTP URLs

The easiest way to get the HTTP/HTTPS version of any URL.

ryanjbonnell

<p>This plugin transforms any registered, enqueued CSS or JavaScript URLs into their “protocol-relative” equivalent.</p>
<p>Consider the following examples:</p>
<p><strong>Protocol Relative CSS URL</strong></p>
<pre><code><link href="//example.com/wp-content/themes/twentytwelve/style.css" />
</code></pre>
<p><strong>Protocol Relative Javascript URL</strong></p>
<pre><code><script src="//example.com/wp-includes/js/jquery/jquery.js"></script>
</code></pre>
<p>More appropriately called a “network-path reference” or “scheme-relative path”, a protocol-relative URL helps to avoid common scenarios such as:</p>
<ul>
<li>Broken SSL padlock icon in browser’s address bar when showing mixed HTTP/HTTPS content</li>
<li>Error message in Internet Explorer saying, “This Page Contains Both Secure and Non-Secure Items”</li>
<li>Serving HTTP assets when viewing HTTPS pages</li>
</ul>
<p>The idea of using protocol-relative URLs was popularized by <a href="http://paulirish.com/2010/the-protocol-relative-url/" rel="nofollow ugc">Paul Irish</a> and has become common as sites switch between serving HTTP and HTTPS assets.</p>
<p>This plugin will standardize all properly enqueued theme files to use protocol-relative paths, even those added from third-party plugins.</p>
<p><em>Note: This plugin does not transform any image paths that may be embedded in the WordPress editor or output as featured images or elsewhere in the theme — it presently only works on enqueued CSS/JavaScript files.</em></p>


Protocol Relative Theme Assets

Transforms enqueued CSS and JavaScript theme URLs to use protocol-relative paths.

HTTP URLs vs Protocol Relative Theme Assets