News for hackers. Stuff that matters.
Re:Chrome 56 will mark HTTP pages with password fields as no... by gregmac on Sunday January 22, 2017 @08:22PM (#13458923)
I was also thinking of the opposite: submitting from an https-loaded page to an http page. I can't imagine why any application would do this (other than by mistake), but it would ideally be flagged as insecure as well.
Re:Chrome 56 will mark HTTP pages with password fields as no... by Wilya on Sunday January 22, 2017 @09:18PM (#13459194)
It's already the case most of the time. If you submit via a plain form (without js), you get the (old) "This page is encrypted, but the information you submitted will be sent unencrypted" message. If you submit via an XMLHttpRequest, it should be blocked as Mixed Content.