Marking HTTP Pages as "Not Secure"

February 9, 2018 #http #webdev #security

Chromium Blog: A secure web is here to stay put a deadline for marking HTTP as “Not Secure”:

Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure”.

What if you want that behavior today?  Below are the configurations to change along with what it looks like accessing the intentionally “not secure”

In Chrome go to chrome://flags and search for mark-non-secure-as

Chrome settings

Chrome "Not Secure"

In Firefox go to about:config and search for security.insecure_connection

Firefox settings

Firefox "Not Secure"

Kevin Hakanson

Multi-Cloud Certified Architect | DevSecOps | AppSec | Web Platform | Speaker | Learner | Builder
Twitter | LinkedIn | GitHub | Stack Overflow | Credly

© 2024 Kevin Hakanson (built with Gatsby)