There is no doubt that the SSL certificate (Secure Socket Layer) is one of the most important security elements for anyone who has a website or blog, as it is responsible for encrypting the information exchanged between an internet page and the end user, guaranteeing, in turn, the confidentiality of personal and professional data , such as numbers credit cards and important documents.
Furthermore, after SSL became one of Google's requirements to better position a website (IF THE) on its results pages and Google Chrome started flagging sites without the certificate as insecure, the number of sites that adhered to the security protocol grew even more.
But sometimes, even after the user hires a SSL certificate or use free certificates for your website, it continues to be marked as unsafe for browsing. At this point it is normal to become very frustrated and think that SSL is not fulfilling its role. The question is: how to solve?
However, what usually happens is a conflict generated by the Mixed Content, something that can be easily resolved in hosting. When a website receives the SSL certificate, it also lets you have the HTTP prefix (port 80) at the address, which is the default, and now has the HTTPS protocol (port 443), which offers an extra layer of protection at all authentication and access steps.
Naturally, the fact that the home page has HTTPS (443) would be enough for it to be considered secure, but what often happens is that there are appointments and content provided by an unsecured source, which only has the HTTP (80) protocol.
In other words, even if you have linked an SSL certificate and your website is already HTTPS, if there are videos, scripts or any other derivative material of an HTTP page, browsers will likely see your site how unreliable. In short, it is this mixture of HTTP and HTTPS content to display the same page that we call mixed content.
How mixed content is generated by HTTP content aggregated with HTTPS, the best solution is to find all the divergent material and make the correction, changing paths HTTP over other HTTPS. This way, the entire website will have notes that will be certified by SSL and can be considered secure.
Hope this helps!
Share the article and leave your comments! 🙂
