This is the risk you need to decide for yourself. That is an easy way to understand the difference between a page served over HTTP and a page served over a secure HTTPS page.įor some websites, this may not be a problem. In this case, it is very unlikely that anyone listening would hear anything that makes sense. You tell her the same secret, but this time you tell it quietly and in a secret language only you and she understand. Now, imagine that you and your friend are at the same coffee shop. Everyone around you can hear it, and therefore, it’s probably not a secret anymore. You and your friend are sitting in the middle of a busy coffee shop and your friend tells you a secret.
This can lead to trust issues with customers, or people visiting your website.Ī simple way to think of HTTPS vs HTTP and insecure pages is this example. If you use the Google Chrome browser, you’ve probably already visited at least one website that your browser told you was “Not secure.” It is difficult to miss these warnings since Google Chrome displays it right next to the website’s URL. Now, all HTTP traffic is viewed as insecure.
These changes have officially taken place. Google has been warning website owners for years that they will soon prefer HTTPS (Hypertext Transfer Protocol Secure) traffic over HTTP.
0 kommentar(er)
