Tweet
Why does the security lock (orange) change to unsecured when I navigate using the Home Page (red) tab? It stays secured when navigating through the site using the circled green tabs, or the Android back arrow, but not the Home Page tab. I'm not using tapatalk, I click on the three dots and changed the view to desktop.
-
Last edited by tony270; 02-25-2021, 5:50 PM. -
it is doing the same for mesigpic -
Device? Browser?Comment
-
Why does the security lock (orange) change to unsecured when I navigate using the Home Page (red) tab? It stays secured when navigating through the site using the circled green tabs, or the Android back arrow, but not the Home Page tab. I'm not using tapatalk, I click on the three dots and changed the view to desktop.
It may be the case that you are using an (Samsung) Android with a Chromium-based browser requesting sites in Desktop mode through the App.
Answer: Human error.
When you click the home button, in particular, the browser accepts certificates from a large number of CAs. You land on the site's login page and momentarily are being 'redirected' because not all elements where being pulled as HTTPS, there is briefly mixed content, (as your origin was not https to begin with) and so there is (momentarily) mixed content of elements being pulled until fully redirected and until fully redirected there is an 'somewhat' invalid certification in transit.
The wildcard is replaced and your browser has made the key exchange and ultimately the CommonName in the certificate matches the https domain in the URL.
Observe this:
In contract to this:
Comment
-
-
WoW, that was extremely helpful, explanation that a 5 grader could understand, thanks.It may be the case that you are using an (Samsung) Android with a Chromium-based browser requesting sites in Desktop mode through the App.
Answer: Human error.
When you click the home button, in particular, the browser accepts certificates from a large number of CAs. You land on the site's login page and momentarily are being 'redirected' because not all elements where being pulled as HTTPS, there is briefly mixed content, (as your origin was not https to begin with) and so there is (momentarily) mixed content of elements being pulled until fully redirected and until fully redirected there is an 'somewhat' invalid certification in transit.
The wildcard is replaced and your browser has made the key exchange and ultimately the CommonName in the certificate matches the https domain in the URL.
Observe this:
In contract to this:
Comment
-
There are currently 18417 users online. 37 members and 18380 guests.
Most users ever online was 239,041 at 10:39 PM on 02-14-2026.
Comment