On the omnibox of Google Chrome, there should be a "Secure" word that indicates the site is secure.
As a whole, mwomercs.com is secure. However threads don't have that.
1
Individual Threads Are Not Secure.
Started by The6thMessenger, Jul 06 2017 05:08 AM
3 replies to this topic
#1
Posted 06 July 2017 - 05:08 AM
#2
Posted 06 July 2017 - 10:55 PM
And in Edge I do NOT have a secure indicator, but the URL starts with HTTPS.
hmm.
Ah, that will mean the PAGE is secure, but some of the referenced content is not.
A pile of calls to various google.com domains, and a call to imgur.com
hmm.
Ah, that will mean the PAGE is secure, but some of the referenced content is not.
A pile of calls to various google.com domains, and a call to imgur.com
Edited by David Sumner, 06 July 2017 - 11:52 PM.
#3
Posted 07 July 2017 - 08:07 PM
Firefox also says parts of the page are unsecure, but I don't know enough web witchcraft to contribute more than that. =)
#4
Posted 21 July 2017 - 09:31 AM
The6thMessenger, on 06 July 2017 - 05:08 AM, said:
On the omnibox of Google Chrome, there should be a "Secure" word that indicates the site is secure.
As a whole, mwomercs.com is secure. However threads don't have that.
As a whole, mwomercs.com is secure. However threads don't have that.
This is being caused by 2nd-party/3rd-party failures to call or return data in 'https'/Secure mode. Unfortunately, that includes people's images in their signatures, including your own (as of when I'm typing this, anyway)... I've got the same issue on another site directly because an image provider won't function in https mode. It's been somewhat annoying, but until website developers have enough respect to all go 'https'/Secure, we're all going to have to live with it.
~D. V. "Waiting for Google's shaming of Non-'https' to reach far enough..." Devnull
[Edit by Post Author for a Minor Wording Error...]
Edited by D V Devnull, 21 July 2017 - 09:32 AM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users