Certificate issued to *.wordpress.com causes issues with reblog Read More link

• 

  elkement · Member · May 17, 2013 at 9:12 am

  • Copy link
  • Add topic to favorites

  I believe I have found a bug in wordpress.com’s reblog feature. The Read More link in the reblog has https[reblogged post] as a target, not http[reblogged pist]. However the certificate used here is a wildcard certificate issued to *.wordpress.com. This means you will get all kinds of errors and Firefox will hardly let you click on the URL unless you confirm all Those Dangerous Exceptions if you reblog a post hosted on a site with a custom domain name.
  This reblog of mine gives proof of the bug: http://elkement.wordpress.com/2013/05/17/the-blahs-4-geek-of-the-year/

• 

  elkement · Member · May 17, 2013 at 12:31 pm

  • Copy link

  … what I forgot on my original comment: I would suggest to link to the reblogged post using http, not https – than anything would work fine.
  I would be interested in the reason for using SSL here.
  (I am an IT security consultant so please don’t hesitate in throwing jargon at me :-))
  Thanks in advance,
  Elke

• 

  elkement · Member · May 17, 2013 at 7:00 pm

  • Copy link

  I could probably resolve it to some extent – but I would still be interested in your comment / explanation / answer to a remaining question:

  It seems the URL to the reblogged post is displayed as https only if I access my blog via SSL. Thus the issues occur if you start out at:
  https://elkement.wordpress.com/2013/05/17/the-blahs-4-geek-of-the-year/
  The issue does NOT occur using the http version of that URL (as shown in my first post here) as the URL to the reblogged post is dynamically re-configured to a http URL

  So the remaining queston is: Why is the URL to the reblogged post changed to https if my blog is accessed via SSL?

  Thanks,
  Elke

• 

  amightywp · Member · May 17, 2013 at 9:14 pm

  • Copy link

  Hi there,

  While you can indeed view your front-end site via SSL, the SSLs which we have installed are there for the purpose of securing all back-end communications. As such, we don’t actually guarantee the full functionality nor have we fully tested the behavior of the front of site over SSL.

  I apologize for any inconvenience!

• 

  elkement · Member · May 17, 2013 at 9:19 pm

  • Copy link

  Thanks for the quick reply. It’s not a big convenience ;-)

  I am just curious why the URL to the reblogged post changes dynamically from http to https when I access my post over SSL.

• 

  elkement · Member · May 17, 2013 at 9:41 pm

  • Copy link

  … should be “inconvenience” of course, sorry!