Manage cookies that are used for advertising, such as ad personalization, remarketing, and ad effectiveness analysis.
2.15.1.2.4. Mixed content
Important points:
- The presence of mixed content is not related to the SSL certificate used.
- Setting up a redirect to HTTP/HTTPS will not solve the mixed content problem (since it does not change the protocol in links on the site's pages); manipulations with the site itself are required.
Mixed content pages are site pages that open using the HTTPS protocol but contain elements (such as styles, scripts, images) that are requested via links using the HTTP protocol. The browser marks such pages as not fully secure or unsecure and may block the loading of such elements. As a result, the site may not display or function correctly.
You can check for mixed content on the current page of the site in the developer tools in your browser. The toolbar opens by pressing F12 or Ctrl+Shift+C. The information is displayed in the "Console" and "Security" tabs:
To solve the problem, you need to replace the HTTP protocol with HTTPS in all links on the site. Depending on the internal structure of the site and the CMS used, different actions may be required:
- Checking the correctness of SSL settings directly in the CMS used.
- Use of specialized CMS plugins.
- Manually search for and replace the protocol in the site files and/or its database.
Examples of instructions for popular CMS: