WordPress Trac: Ticket #22811: Make WordPress.org's links use http or https by auto-detectionhttps://core.trac.wordpress.org/ticket/22811
<p>
WordPress.org's links are hardcoded to use the http protocol despite the pages also being viewable using https (which is great). This causes unwanted hassle with eg. bookmarks, showing which pages were or were not visited and so forth.
</p>
<p>
An example of the steps to reproduce:
</p>
<ol><li>Go to a https URL (eg. <a class="ext-link" href="https://wordpress.org/extend/plugins/search.php?q="><span class="icon">​</span>https://wordpress.org/extend/plugins/search.php?q=</a> with the search string appended after the "=", this being the only way to search on WordPress.org via https as all the forms redirect to http).
</li><li>Type anything in any of the search forms.
-&gt; A warning is shown that you're being redirected to an unencrypted page.
</li></ol><p>
OR
</p>
<ol start="3"><li>Go to a https URL (eg. <a class="ext-link" href="https://wordpress.org/extend/plugins/types/"><span class="icon">​</span>https://wordpress.org/extend/plugins/types/</a> ).
</li><li>Bookmark the page. Imagine a few months happening before the next step.
</li><li>Click the Description tab (when browsing normally you'd click another tab in between but it's not a necessary step here).
</li><li>You're now on a page that you haven't bookmarked. Bookmark it, because you like this page and don't remember having bookmarked a rather identical page months ago.
</li><li>You end up having multiple bookmarks for the same pages.
</li></ol><p>
The fix for all these is rather easy on paper: have all links on wordpress.org that point to wordpress.org automatically use the protocol used for loading the page currently being viewed. Start with having forms' targets use this, then navigational links, and later consider either auto-converting links in page contents (eg. plugin descriptions) or mentioning the possibility of using <tt>://</tt> links for this next to editors.
</p>
en-usWordPress Trachttps://core.trac.wordpress.org/chrome/site/your_project_logo.pnghttps://core.trac.wordpress.org/ticket/22811
Trac 1.0.1SergeyBiryukovFri, 07 Dec 2012 15:54:45 GMTdescription, milestone changedhttps://core.trac.wordpress.org/ticket/22811#comment:1
https://core.trac.wordpress.org/ticket/22811#comment:1
<ul>
<li><strong>description</strong>
modified (<a href="/ticket/22811?action=diff&amp;version=1">diff</a>)
</li>
<li><strong>milestone</strong>
changed from <em>Awaiting Review</em> to <em>WordPress.org</em>
</li>
</ul>
TicketwebawareThu, 13 Dec 2012 02:03:20 GMThttps://core.trac.wordpress.org/ticket/22811#comment:2
https://core.trac.wordpress.org/ticket/22811#comment:2
<p>
This has another impact, on searches from DuckDuckGo. If you search using bang notation, !wp, DuckDuckGo sends you to an https link, which fails to load any results due to insecure content (including scripts, CSS, images).
</p>
<p>
Try for yourself: <a class="ext-link" href="http://duckduckgo.com/?q=!wp+wp_enqueue_script"><span class="icon">​</span>http://duckduckgo.com/?q=!wp+wp_enqueue_script</a>
</p>
TicketwycksWed, 03 Apr 2013 23:38:20 GMThttps://core.trac.wordpress.org/ticket/22811#comment:3
https://core.trac.wordpress.org/ticket/22811#comment:3
<p>
+1
</p>
<p>
Also you don't need any special URL, just go to <a class="ext-link" href="https://wordpress.org/extend/plugins/"><span class="icon">​</span>https://wordpress.org/extend/plugins/</a> for example and it won't load approximatly 13 files (css, js,).
</p>
<p>
Another issue are people using the "HTTPS Everywhere" Chrome and Firefox plugins, and I think some of the AD removers also force HTTPS when available.
</p>
<p>
I think it's best to either turn it off or make it work.
</p>
TicketSergeyBiryukovMon, 15 Apr 2013 15:32:08 GMThttps://core.trac.wordpress.org/ticket/22811#comment:4
https://core.trac.wordpress.org/ticket/22811#comment:4
<p>
<a class="closed ticket" href="https://core.trac.wordpress.org/ticket/24091" title="defect (bug): HTTPS is broken on wordpress.org (closed: duplicate)">#24091</a> was marked as a duplicate.
</p>
TicketfulldecentMon, 15 Apr 2013 15:34:43 GMThttps://core.trac.wordpress.org/ticket/22811#comment:5
https://core.trac.wordpress.org/ticket/22811#comment:5
<p>
From duplicate <a href="https://core.trac.wordpress.org/ticket/24091">https://core.trac.wordpress.org/ticket/24091</a>
</p>
<p>
This shows what the page looks like when loaded from the https URL.
</p>
<p>
<a href="https://core.trac.wordpress.org/attachment/ticket/24091/Screen%20Shot%202013-04-15%20at%2011.15.19%20AM.png">https://core.trac.wordpress.org/attachment/ticket/24091/Screen%20Shot%202013-04-15%20at%2011.15.19%20AM.png</a>
</p>
TicketiandunnThu, 11 Jul 2013 16:48:53 GMTcc sethttps://core.trac.wordpress.org/ticket/22811#comment:6
https://core.trac.wordpress.org/ticket/22811#comment:6
<ul>
<li><strong>cc</strong>
<em>ian.dunn@…</em> added
</li>
</ul>
TicketwycksSat, 10 Aug 2013 20:52:14 GMThttps://core.trac.wordpress.org/ticket/22811#comment:7
https://core.trac.wordpress.org/ticket/22811#comment:7
<p>
It seems some progress has been done here but one page still breaks the layout( I did not test all of them), <a class="ext-link" href="https://wordpress.org/showcase/"><span class="icon">​</span>https://wordpress.org/showcase/</a>
</p>
<p>
Also &lt;img&gt; tags still load over HTTP.
</p>
TicketiandunnSun, 11 Aug 2013 20:57:36 GMThttps://core.trac.wordpress.org/ticket/22811#comment:8
https://core.trac.wordpress.org/ticket/22811#comment:8
<p>
Before this can be done, s.wordpress.org will need an SSL certificate setup (<a class="ext-link" href="https://meta.trac.wordpress.org//intertrac/ticket%3A72" title="ticket:72 in Making WordPress.org Trac"><span class="icon">​</span>#meta72</a>).
</p>
TicketDaedalonMon, 12 Aug 2013 10:40:18 GMThttps://core.trac.wordpress.org/ticket/22811#comment:9
https://core.trac.wordpress.org/ticket/22811#comment:9
<p>
Fulldecent: Unfortunately clicking that .png link or the ticket link only leads me back to this page. Perhaps a WP Trac maintainer could be notified of this odd behavior somehow?
</p>
<p>
In the meanwhile, if anyone has a copy of that attachment, could it be added to this ticket?
</p>
Ticketocean90Mon, 12 Aug 2013 10:52:57 GMThttps://core.trac.wordpress.org/ticket/22811#comment:10
https://core.trac.wordpress.org/ticket/22811#comment:10
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/22811#comment:9" title="Comment 9 for Ticket #22811">Daedalon</a>:
</p>
<p>
Works for me. The image is also attached to <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/24091" title="defect (bug): HTTPS is broken on wordpress.org (closed: duplicate)">#24091</a>.
</p>
TicketDaedalonMon, 12 Aug 2013 11:11:17 GMThttps://core.trac.wordpress.org/ticket/22811#comment:11
https://core.trac.wordpress.org/ticket/22811#comment:11
<p>
Thanks, Ocean90. Now it works for me too. Previously did not, neither before or after login.
</p>
TicketOtto42Tue, 20 Aug 2013 11:55:17 GMTstatus changed; resolution set; milestone deletedhttps://core.trac.wordpress.org/ticket/22811#comment:12
https://core.trac.wordpress.org/ticket/22811#comment:12
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>maybelater</em>
</li>
<li><strong>milestone</strong>
<em>WordPress.org</em> deleted
</li>
</ul>
<p>
These will need to be handled on a case by case basis. Make new tickets on meta.trac as necessary.
</p>
TicketOtto42Tue, 20 Aug 2013 17:09:46 GMTresolution changedhttps://core.trac.wordpress.org/ticket/22811#comment:13
https://core.trac.wordpress.org/ticket/22811#comment:13
<ul>
<li><strong>resolution</strong>
changed from <em>maybelater</em> to <em>fixed</em>
</li>
</ul>
<p>
Showcase site mostly fixed. Any further sites showing this same issue (incorrect use of http for CSS/images when browsing via https) should receive their own separate tickets on meta.trac.
</p>
Ticket