We've made an update to how redirects and interlinking works in regards too https vs http. The server will always attempt too use https now, rather than continue on with whichever it was given in the first place. This should reduce the number of pages that browsers call insecure.
The reason it cannot be 100% coverage for all links across all sites is because some of the content that you like to use is not over https. This also includes any custom content you may have on custom pages or HTML widgets. If you have a background image that comes from an http URL, browsers will call that image insecure and may call the entire page insecure as a result. We very much want to keep GamerLaunch an open platform that allows you to make the website you want and include the content you want. We will not be blocking http content because that would limit your sites in an untenable way.
Another complication to this is custom domains. If you've bought a custom URL to use for your site, it presents another layer of security to consider. We are evaluating ways to provide custom URL's with SSL certs as a paid service. Contact us through support if you are interested.
I'd be interested to know how a paid for certificate for a paid for domain name would affect the site. Would that basically bring it into line with other sites that use the gamer launch domain names? ie, some of the pages would still show as being insecure if they have custom content on them?
How would that affect the page and visitors to it?
Would there be a way of tracing which content on a page may affect the https status, and potentially allow for an alternative to be found?
This is a very complicated subject and I'm going to try my best here haha.
Sites on our official domains have always had fully secure login pages because we do not allow any custom content on those pages, it's fully internal and secure.
The update we made today is to make ALL internal resources and links within GamerLaunch to be https URLs.
The message the browser will give you for something like this will look like this:
A way to see exactly what is causing the browser to give you that warning is too look in the dev console. The message will look something like this:
Zam tooltip hovers is cool and a useful tool, we aren't going to stop using them just because Google is overbearing with their security messaging.
That should fairly cover what the actual "problem" is here.
If you were to acquire an SSL Cert for your own custom domain URL, the website would behave exactly the same as above.
I really hope this does not just further confuse you haha.