Unless using a browser extension (egː HTTPS Everywhere), it is up to the website owner to configure automatic transition from http to https on their website.
One flaw to using //website.com , is that the link is not automatically created. It will display as normal article text. This is not a huge deal, as most of the links the wiki uses have a different name than their web address.
http://example.com uses only http - the web master has not set up transition to HTTPS, but is supported.
https://example.com attempts a secure connection. We explicitly told the browser to use https.
//example.com has a valid HTTPS certificate, and HTTPS is used - even though we did not specify.
We can make the browser use HTTPS, if available for the Ontario Government's website:
//ontario.ca
Sometimes, an invalid certificate message may appear.
//scdsb.on.ca
In this example for the SCDSB website, the site is misconfigured. The certificate is only valid for www.scdsb.on.ca , and not scdsb.on.ca . It is VERY important to check that links work before publishing a wiki article. We now know //www.scdsb.on.ca is the better version to use.
Let's check out Place Browser:
http://w-tools.org - automatically switches to HTTPS. HOWEVER, the request can be intercepted by someone on the same network as you. Such as a coffee shop, or library. For more information on
//w-tools.org - uses HTTPS - we should use this version.
Did you know?: A captive portal does NOT make the network secure to use, it is just a form of authentication to limit the amount of users, or to accept terms of use.
//BraydenPeacock.ca/waze
http://BraydenPeacock.ca/waze
https://BraydenPeacock.ca/waze
Fun fact: Websites can, although not beneficial, have a valid HTTPS certificate which can redirect you to the HTTP version. Very few sites do this, as it is less secure.