It makes sense though?
If you're browsing via HTTP there is no expectation at all that what you are doing is secure.
If you have a problem in HTTPS, you are expecting to be secure, you might not be. Hence, a warning.
If you're browsing via HTTP there is no expectation at all that what you are doing is secure.
If you have a problem in HTTPS, you are expecting to be secure, you might not be. Hence, a warning.
No comments yet.