9 posts
|
This post was updated on Oct 02, 2019; 1:18pm.
Yes @ GregChapman, this looks to be the same issue.
When you enforce https to be used, any code being served through this, requires to be served using the same protocol, https.
So because the code served still contains http requests, they are being blocked due to mixed content.
I was expecting that with the request to turn my forum into https, the code served would have been fixed to contain only https requests, which is not the case. It appears only the top call was changed, not the content.
This is clearly the case for the embed code itself, now served over https, containing http calls.
This is however also the case for the calls made to Google's font servers, which you clearly show in your post linked.
I am hoping that Nabble will not only make a change to https at the top level for those who request to use the secure protocol, but also provide cleaned up code where any http call is changed accordingly.
I am sorry I missed your post Greg or I would have left a reply.
Either way, I think the discussion might as well be done here, as the issue is a logical result of the move to https, which we request here.
|