3 ms·
Agreed. I'm sure Google will take that into account if they decide to ramp-up the prominence of the 'warning'. As it is, the warning seems to be disabled for l
by MaxBarraclough 8y ago
Agreed. I'm sure Google will take that into account if they decide to ramp-up the prominence of the 'warning'.
As it is, the warning seems to be disabled for localhost/127.0.0.1 (where I only see a 'not secure' if I manually click the ⓘ) but the warning shows as usual if I browse a local IP address over plaintext HTTP.