Jetpack: Shortlinks: wp.me always redirects to http, even if site uses HTTPS

Created on 14 Jan 2015 · 7Comments · Source: Automattic/jetpack

Steps to reproduce:

Connect a full-https site to WordPress.com via Jetpack.
Check the wp.me shortlink of one of the posts. It redirects to the http shortlink. Here is an example:

$ curl -I http://wp.me/p4LPVl-3PY
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Wed, 14 Jan 2015 13:35:28 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Location: http://www.liveroomescape.com/?p=14754

Reported here:
https://wordpress.org/support/topic/publicize-facebook-links-are-not-secure-for-https-site?replies=3

Shortlinks [Status] Stale [Type] Bug

Source

jeherve

All 7 comments

Yes this indeed an wired bug. Looking to be fixed in the next update.

isaumya on 19 Jan 2015

Is this bug still being looked at? I'm still seeing it in the latest version of WordPress and links posted to Facebook and Twitter are showing a http:// link, rather than https://.

alexryans on 9 Apr 2016

👍1

@alexryans Very good question. I've almost forgot that I've ever replied on this issue as there is almost no replies. Besides the time shows "Future", which could be in the year 2166 :wink: when Vandal Savage will concur the earth :smile:

isaumya on 9 Apr 2016

As a fan of Legends of Tomorrow, I 100% appreciate that reference, @isaumya. I do, however, hope it's fixed much sooner than that!

alexryans on 9 Apr 2016

😄1

@alexryans @isaumya We haven't looked at it yet, but we'll see if we can get this resolved in a future release. We'll update this issue as soon as we make progress.

You can rest assured, we'll get this fixed before 2166. If all else fails, we'll have The Flash go back in time and fix the bug on January 13, 2015, before I even opened it ;)

jeherve on 11 Apr 2016

😄1

This issue has been marked as stale. This happened because:

It has been inactive in the past 6 months.
It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.