{"id":5597837,"date":"2014-12-20T13:13:13","date_gmt":"2014-12-20T13:13:13","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/unsecure-content-via-https\/"},"modified":"2016-08-22T13:43:11","modified_gmt":"2016-08-22T13:43:11","slug":"unsecure-content-via-https","status":"closed","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/unsecure-content-via-https\/","title":{"rendered":"Unsecure content via HTTPS"},"content":{"rendered":"<p>Hi.<\/p>\n<p>As posted here:<\/p>\n<p>https:\/\/wordpress.org\/support\/topic\/plugin-digg-digg-ssl-support?replies=3<\/p>\n<p>running the latest version still calls e.g. the twitter widgets.js via http, although the page is called via https.<br \/>\nFirefox is complaining about that as an unsecure site.<br \/>\nIs there something that fixes this?<\/p>\n<p>https:\/\/wordpress.org\/plugins\/digg-digg\/<\/p>\n","protected":false},"template":"","class_list":["post-5597837","topic","type-topic","status-closed","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/5597837","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/5597837\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=5597837"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}