Here is the start of httpsJanuary 27, 2017
A DevHub analyst got the following note via Google - that non secure collection of passwords will begin to trigger warnings in Chrome 56.
From Google →
Beginning in January 2017, Chrome (version 56 and later) will mark pages that collect passwords or credit card details as “Not Secure” unless the pages are served over HTTPS.
The following URLs include input fields for passwords or credit card details that will trigger the new Chrome warning. Review these examples to see where these warnings will appear, and so you can take action to help protect users’ data. The list is not exhaustive…
The new warning is the first stage of a long-term plan to mark all pages served over the non-encrypted HTTP protocol as “Not Secure”.
Learn how DevHub solves for SSL across Web Experience:
DevHub is the standard for managing web experience: one-to-many. Not only are the changing standards of the web moving faster - but the opportunity to gain a competitive advantage through compliance could provide a significant lift to performance.