{"id":8784979,"date":"2017-02-09T10:15:23","date_gmt":"2017-02-09T10:15:23","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/mixed-content-warning-on-https\/"},"modified":"2017-02-09T10:15:23","modified_gmt":"2017-02-09T10:15:23","slug":"mixed-content-warning-on-https","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/mixed-content-warning-on-https\/","title":{"rendered":"mixed-content warning on https"},"content":{"rendered":"<p>Ciao Stefano!<\/p>\n<p>I recently moved my website to https.  It&#8217;s hosted on Siteground using their server caching (SuperCacher), and also piped thorugh Cloudflare &#8220;plus&#8221; using &#8220;strict SSL protocol&#8221; for additional CDN services.<\/p>\n<p>I would still like to continue using Hypercache to lower server load and serve cache 404 error pages.<\/p>\n<p>In the Hypercache options, for https I chose to create a separate cache. When supercacher is running I don&#8217;t see the &#8220;green lock&#8221; that confirms fully secure website content in Chrome&#8217;s address bar.  Instead, I see the &#8220;i&#8221; in a circle which is a mixed- content warning.<\/p>\n<p>What settings should I be using to prevent this?<\/p>\n<p>Ciao,<\/p>\n<p>L<\/p>\n","protected":false},"template":"","class_list":["post-8784979","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/8784979","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\/8784979\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=8784979"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}