{"id":11953,"date":"2020-01-14T13:30:00","date_gmt":"2020-01-14T18:30:00","guid":{"rendered":"https:\/\/www.thesslstore.com\/blog\/?p=11953"},"modified":"2023-05-25T12:28:26","modified_gmt":"2023-05-25T16:28:26","slug":"how-to-find-and-fix-mixed-content-warnings-on-https-sites","status":"publish","type":"post","link":"https:\/\/www.thesslstore.com\/blog\/how-to-find-and-fix-mixed-content-warnings-on-https-sites\/","title":{"rendered":"How to Find and Fix Mixed Content Warnings on HTTPS Sites"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\" id=\"h-simply-supporting-https-isn-t-always-enough-you-also-need-to-know-how-to-identify-and-fix-mixed-content-errors\">Simply\nsupporting HTTPS isn\u2019t always enough \u2014 you also need to know how to identify\nand fix mixed content errors<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you recently migrated your website from an insecure HTTP connection to a more secure <a href=\"https:\/\/www.thesslstore.com\/blog\/what-is-a-website-security-certificate-and-what-does-it-do-for-your-business\/\">HTTPS connection<\/a>, you may still run into the problem of receiving mixed content warnings. Worse yet, your site may render as insecure to site visitors, causing them to quickly click the \u2018back\u2019 button and find elsewhere to explore.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That said, the real problem with mixed content warnings on HTTPS\nconnections is emerging with Google Chrome\u2019s latest release \u2014 Chrome 79. With this new release, some\ncontent that continues to load over an insecure connection will automatically\nbe blocked. It will mark websites that use TLS 1.0 or 1.1 as &#8220;Not\nSecure&#8221; and no longer show the lock icon for them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Further down the road with Chrome 81, scheduled to be released <a rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\" href=\"https:\/\/blog.chromium.org\/2019\/10\/chrome-ui-for-deprecating-legacy-tls.html\" target=\"_blank\">sometime in March<\/a>, Google will completely remove support for the legacy TLS protocol, which will block all non-secure content by default. In other words, content on your site that is not loading via HTTPS will not load at all, and your site visitors will not see this content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to make sure all your site\u2019s content is loading over a\nsecure connection and site visitors see it all, keep reading. Today we\u2019re\nexplaining <strong>what mixed or insecure\ncontent is<\/strong>, why it\u2019s a problem, and <strong>how\nto find and fix mixed content warnings<\/strong> if you see them on your HTTPS\nwebsite.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s hash it out.<span id=\"newline\"><\/span><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"display:none\" class=\"tl-placeholder-f-type-shortcode_12753\"><\/span><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-what-is-mixed-content\">What Is Mixed Content?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/developers.google.com\/web\/fundamentals\/security\/prevent-mixed-content\/what-is-mixed-content\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\">According to Google<\/a>, mixed content occurs when HTML on a website loads over a secure HTTPS connection (thanks to a recently installed SSL certificate) but other content, such as images, video content, stylesheets, and scripts, continue to load over an insecure HTTP connection. This results in <strong>some web content loading securely and some web content loading insecurely<\/strong>. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hence the name \u201cmixed\ncontent.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The thing with mixed or insecure content is that it all loads over\na secure HTTPS connection, whether the content itself is secure or not. And\nwhen this happens, modern browsers such as Google Chrome display warnings to\nusers trying to view the web content that the site contains insecure content.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"900\" height=\"500\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-mixed-content.png\" alt=\"Graphic: A collage of mixed content error messages on websites\" class=\"wp-image-11960\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-mixed-content.png 900w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-mixed-content-300x167.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-mixed-content-768x427.png 768w\" sizes=\"auto, (max-width: 900px) 100vw, 900px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Secure websites that load over HTTPS connections provide the\nfollowing benefits:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Authentication. <\/strong>Reassure your site visitors that they\u2019re safe when they land on\nyour website and engage with your site content, especially if you run an online\nshop where financial information is shared. In addition, verify for site\nvisitors that they\u2019re on the website they want to be and haven\u2019t been redirected\nto a malicious site. <\/li>\n\n\n\n<li><strong>Data Integrity.<\/strong> Visually tell site\nvisitors that their personal and financial information is secure and safe from\nhackers no matter what action they take on your site. In addition, give\nbrowsers the ability to detect whether a hacker has changed any data a browser\nreceives. In other words, help users trust that a hacker hasn\u2019t redirected\nmoney paid via your online store to another account.<\/li>\n\n\n\n<li><strong>Anonymity.<\/strong> Guarantee site visitors that\ntheir behavior while on your site isn\u2019t being intercepted by others and used\nmaliciously.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In short, HTTPS allows website owners to secure their data and build trust with those that visit their site so they can continue to build their brand and business.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-why-is-mixed-content-a-security-issue\">Why Is Mixed Content a Security Issue?<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"144\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/google-mixed-content-example-1024x144.jpg\" alt=\"Graphic: A screenshot example of a mixed content error\" class=\"wp-image-11954\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/google-mixed-content-example-1024x144.jpg 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/google-mixed-content-example-300x42.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/google-mixed-content-example-768x108.jpg 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/google-mixed-content-example.jpg 1075w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">(Image source: <a rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\" href=\"https:\/\/developers.google.com\/web\/fundamentals\/security\/prevent-mixed-content\/what-is-mixed-content\" target=\"_blank\">https:\/\/developers.google.com\/web\/fundamentals\/security\/prevent-mixed-content\/what-is-mixed-content<\/a>) <\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">If mixed content loads over a secure connection, you may be asking\nyourself why it matters. <em>After all, the\nHTTPS connection should be securing the resources regardless of whether it\u2019s\nmixed or not, right?<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wrong.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Any time there is mixed or insecure content on a webpage, the\nentire website becomes vulnerable to attack. While it doesn\u2019t open the webpage\nup to all types of cybercrime, it weakens the overall security of the site.\nThis means that if a hacker breaches a website that loads mixed content, they\nmight be able to take control of the entire page, not just the resource that is\ninsecure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">While most modern browsers display mixed content warnings for\npeople to see before they visit a website, the truth is, many of these warnings\ncome too late. In fact, oftentimes hackers have already broken into mixed\ncontent websites and have begun doing damage without the site owners or\nvisitors knowing what\u2019s occurred.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here are some other ways mixed or insecure content on your HTTPS\nsite can become a security problem:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hackers can intercept HTTP requests\nto load an image and swap your site\u2019s image out for another one the hacker\nprefers.<\/li>\n\n\n\n<li>Your \u2018save\u2019 and \u2018delete\u2019 button\nimages can be switched, causing site visitors to accidentally save or delete\ncontent. <\/li>\n\n\n\n<li>The front end of your site can be\ndefaced, which is especially bad when it\u2019s with lewd or inappropriate images or\ntext.<\/li>\n\n\n\n<li>A hacker can intercept written\ncontent and rewrite it entirely.<\/li>\n\n\n\n<li>Passwords, session cookies, and\nother login credentials can become compromised and land in the hands of cybercriminals.<\/li>\n\n\n\n<li>Your site visitors can be\nredirected to another site without knowing any different.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Browsers do their best to block the most dangerous types of mixed\ncontent on websites. However, it\u2019s impossible to block all of it (though that seems like an obvious solution)\nbecause so many well-established and highly trafficked websites render mixed or\ninsecure content for site visitors. Blocking all of it will lead to ruin and\ncause a lot of problems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That said, you can expect popular browsers like Chrome to continue\nto block more and more mixed content as new versions are released.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-how-to-find-and-fix-mixed-content-warnings-on-your-https-website\">How\nto Find and Fix Mixed Content Warnings on Your HTTPS Website<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019ve taken a proactive approach to site security and have installed an <a href=\"https:\/\/www.thesslstore.com\/products\/ssl.aspx\">SSL certificate on your site<\/a>, be proud. Data from <a href=\"https:\/\/transparencyreport.google.com\/https\/overview?hl=en\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\">Google\u2019s Transparency Report<\/a> indicates that desktop users load more than half the pages they visit over HTTPS connections and spend more than two-thirds of their time on HTTPS webpages. <\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"946\" height=\"453\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-connections-by-platform.jpg\" alt=\"Graphic: A Google Transparency Report chart of platforms people use to access HTTPS sites.\" class=\"wp-image-11955\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-connections-by-platform.jpg 946w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-connections-by-platform-300x144.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/https-connections-by-platform-768x368.jpg 768w\" sizes=\"auto, (max-width: 946px) 100vw, 946px\" \/><figcaption class=\"wp-element-caption\"> (Image Source: <a rel=\"noreferrer noopener\" aria-label=\"Google Transparency Report (opens in a new tab)\" href=\"https:\/\/transparencyreport.google.com\/https\/overview?hl=en\" target=\"_blank\">Google Transparency Report<\/a>) <\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Unfortunately, data encryption is less prevalent across mobile\ndevices, though more site owners are taking measures to secure their mobile\nsites as time goes on and mobile usage worldwide continues to climb.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, just because you\u2019ve done the right thing by encrypting\nyour site\u2019s data, doesn\u2019t mean your website\u2019s content is fully secure. That\u2019s\nwhy you must work hard to prevent loading mixed content on your website in the\nfirst place. Otherwise, that SSL certificate does you no good.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s look at <strong>how to find\nand fix mixed content<\/strong> loading on an HTTPS website using Google Chrome. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-step-1-visit-your-website\">Step\n1: Visit Your Website<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Visiting your website to find mixed or insecure content warnings\nmay seem obvious. <em>But, in reality, how\nmany times do you casually visit your own website as though you\u2019re a site\nvisitor?<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s important you check your site first to see if you\u2019re loading\nmixed or insecure content over your secure HTTPS connection. Remember, Google\nChrome will display mixed content warnings if mixed content is present on your\nsite.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To view Chrome\u2019s mixed content warnings, first click on the\nwebpage you want to check. Then, right-click and scroll down to \u2018Inspect\nElement.\u2019 When you do, choose the tab labeled <strong>Console<\/strong>. The browser will detect mixed content and display warnings\nlike this:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"701\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/mixed-content-example-chrome-console-1024x701.jpg\" alt=\"Graphic: A behind-the-scenes look at mixed content\" class=\"wp-image-11959\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/mixed-content-example-chrome-console-1024x701.jpg 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/mixed-content-example-chrome-console-300x205.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/mixed-content-example-chrome-console-768x525.jpg 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/mixed-content-example-chrome-console.jpg 1029w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">(Image source: <a rel=\"noreferrer noopener\" aria-label=\"https:\/\/googlesamples.github.io\/web-fundamentals\/fundamentals\/security\/prevent-mixed-content\/passive-mixed-content.html  (opens in a new tab)\" href=\"https:\/\/googlesamples.github.io\/web-fundamentals\/fundamentals\/security\/prevent-mixed-content\/passive-mixed-content.html\" target=\"_blank\">https:\/\/googlesamples.github.io\/web-fundamentals\/fundamentals\/security\/prevent-mixed-content\/passive-mixed-content.html)<\/a><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">If the mixed content is very serious (meaning it opens up hackers to take complete control over your entire\nweb page), the mixed content warnings will display in red:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"444\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/serious-mixed-content-warning-example-chrome-console-1024x444.jpg\" alt=\"Graphic: A screenshot of a mixed content error\" class=\"wp-image-11956\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/serious-mixed-content-warning-example-chrome-console-1024x444.jpg 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/serious-mixed-content-warning-example-chrome-console-300x130.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/serious-mixed-content-warning-example-chrome-console-768x333.jpg 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/serious-mixed-content-warning-example-chrome-console.jpg 1032w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">(Image source: <a rel=\"noreferrer noopener\" aria-label=\" https:\/\/googlesamples.github.io\/web-fundamentals\/fundamentals\/security\/prevent-mixed-content\/active-mixed-content.html  (opens in a new tab)\" href=\"https:\/\/googlesamples.github.io\/web-fundamentals\/fundamentals\/security\/prevent-mixed-content\/active-mixed-content.html\" target=\"_blank\">https:\/\/googlesamples.github.io\/web-fundamentals\/fundamentals\/security\/prevent-mixed-content\/active-mixed-content.html)<\/a><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The Chrome Developer tools will only display mixed content\nwarnings for the webpage you\u2019re currently viewing. This means you will have to\nmanually inspect every single web page on your website if you want to fix all\nthe mixed content warnings on your site. As you can see, this can be a very\ntime-consuming and tedious task if you don\u2019t catch the problems early on.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-step-2-verify-your-site-s-urls\">Step\n2: Verify Your Site\u2019s URLs<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Besides inspecting the source code on your entire website, another\nsurefire way to identify insecure content on your site, despite having an HTTPS\nconnection, is to check your site\u2019s URLs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you notice that some of your site\u2019s URLs are HTTP instead of\nHTTPS when you <em>know<\/em> that you have an active SSL certificate on your\nsite, then you know there\u2019s likely a problem with some mixed content loading on\nthe front end for site visitors. It\u2019s best to keep a list of all web pages on\nyour site that are loading mixed or insecure content. This will help you stay\norganized when it comes to fixing all the warnings you discover.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-step-3-compare-the-http-vs-https-web-pages\">Step\n3: Compare the HTTP vs HTTPS Web Pages<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once you know mixed content is loading on your HTTPS website, the\nnext thing you\u2019ll want to do is compare your insecure HTTP web page against the\nsecure HTTPS web page (using the same URL for both). If the web pages are\nidentical over HTTP and HTTPS, move on to the next step. This means no content\nis being blocked by Google Chrome and you can move on.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"950\" height=\"370\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/similar-http-and-https-sources.jpg\" alt=\"Graphic: An illustration of mixed content in the browser\" class=\"wp-image-11958\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/similar-http-and-https-sources.jpg 950w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/similar-http-and-https-sources-300x117.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/similar-http-and-https-sources-768x299.jpg 768w\" sizes=\"auto, (max-width: 950px) 100vw, 950px\" \/><figcaption class=\"wp-element-caption\">(Image source: <a rel=\"noreferrer noopener\" aria-label=\"https:\/\/developers.google.com\/web\/fundamentals\/security\/prevent-mixed-content\/fixing-mixed-content#finding_mixed_content_by_visiting_your_site  (opens in a new tab)\" href=\"https:\/\/developers.google.com\/web\/fundamentals\/security\/prevent-mixed-content\/fixing-mixed-content#finding_mixed_content_by_visiting_your_site\" target=\"_blank\">https:\/\/developers.google.com\/web\/fundamentals\/security\/prevent-mixed-content\/fixing-mixed-content#finding_mixed_content_by_visiting_your_site)<\/a><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">If, however, you see a warning or the content will not display\nover the HTTP connection, you should do one of the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Get rid of the resource\naltogether (<em>e.g. the image, video, etc.\nthat will not display over HTTP<\/em>);<\/li>\n\n\n\n<li>Include the resource from another\nhost if available; or<\/li>\n\n\n\n<li>Download and host the resource on\nyour site directly.<\/li>\n<\/ul>\n\n\n<span style=\"display:none\" class=\"tl-placeholder-f-type-shortcode_12653\"><\/span>\n\n\n<h3 class=\"wp-block-heading\" id=\"h-step-4-change-the-url-and-save\">Step\n4: Change the URL and Save<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If your website renders the same over both HTTP and HTTPS\nconnections, the next step is to change the URL from <em>http:\/\/ <\/em>to <em>https:\/\/<\/em>, save\nthe source file and redeploy the updated file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then, click on the web page where the mixed content error appeared\nand make sure it\u2019s fixed and rendering over a secure HTTPS connection. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-ways-to-prevent-mixed-content-warnings-on-your-https-site\">Ways\nto Prevent Mixed Content Warnings on Your HTTPS Site<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">It can be frustrating to install an SSL certificate on your\nwebsite and continue to receive mixed content warnings despite the secure\nconnection. That\u2019s why taking a few additional measures to secure your website,\nand safeguard your site visitors, is sometimes necessary.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-1-always-use-https-urls-when-loading-your-webpages\">1.\nAlways Use HTTPS URLs When Loading Your Webpages<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s important that you apply your HTTPS connection (https:\/\/) to\nall web pages on your website whenever possible. If you notice that your web pages\nare loading over an insecure connection, despite having an active SSL\ncertificate on your site, you need to fix this. This might mean getting in\ntouch with your web hosting provider\u2019s support team if they\u2019re the ones\nproviding you with an SSL certificate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-2-use-the-content-security-policy-report-only-header\">2.\nUse the Content-Security-Policy-Report-Only Header<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to collect reports of mixed content on your website automatically, you might consider adding this snippet of code to your site\u2019s <a href=\"https:\/\/www.thesslstore.com\/blog\/http-security-headers\/\">HTTP response header<\/a>: <\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Content-Security-Policy-Report-Only: default-src https: 'unsafe-inline' 'unsafe-eval'; report-uri https:\/\/example.com\/reportingEndpoint<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Though this isn\u2019t 100% reliable for fixing mixed content before it\nbecomes a problem, it does help those with large websites stay on top of\ninsecure content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When a site visitor lands on a web page that has mixed content, a\nreport is sent to https:\/\/example.com\/reportingEndpoint alerting\nyou that something has violated the content security policy. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The report will include the:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>URL of the webpage in question,\nand<\/li>\n\n\n\n<li>The subresource that violated the policy.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">By configuring your reporting endpoint to log these reports, you\ncan track mixed content on your website without having to visit each webpage\nyourself. That said, the only time this strategy works is if a site visitor\nlands on a web page with mixed content. Not to mention, you\u2019ll only receive\nreports for moderately to highly trafficked web pages, meaning mixed content\nmay be loading for some time before you become aware of it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-3-use-the-upgrade-insecure-requests-csp-directive\">3.\nUse the Upgrade-Insecure-Requests CSP Directive<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Another way to automatically detect and fix mixed content warnings on your HTTPS site before it becomes an issue is to use the <a href=\"https:\/\/developers.google.com\/web\/fundamentals\/security\/prevent-mixed-content\/fixing-mixed-content\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\">upgrade-insecure-requests<\/a> directive tool. This tool tells the browser to upgrade all insecure URLs before making any user requests.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In other words, an insecure URL will be made secure before loading\nfor a site visitor on the front end of your website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To do this, add this meta tag snippet of code to the document\u2019s\nHTML &lt;head&gt; section:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;meta http-equiv=\"Content-Security-Policy\" content=\"upgrade-insecure-requests\"&gt;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Remember, if the resource that is loading via HTTP over an HTTPS\nconnection is not available over HTTPS, this tool will not work. Therefore, the\nresource will not be upgraded as secure and will not load for site visitors.\nThough this means site visitors will miss some of your site\u2019s content, it also\nmeans they remain secure as they explore your site.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-4-use-an-online-tool-to-identify-mixed-content-warnings\">4.\nUse an Online Tool to Identify Mixed Content Warnings<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you have a large website and don\u2019t have the time and manpower\nto do all of the above, you can always use a web crawler service to help\nidentify mixed content warnings on your HTTPS website:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a aria-label=\" (opens in a new tab)\" href=\"https:\/\/www.thesslstore.com\/ssltools\/why-no-padlock.php\" target=\"_blank\" rel=\"noreferrer noopener\">Why No Padlock?<\/a> This free tool will allow you to quickly check your URL to ensure there are no insecure links found on your site.<\/li>\n\n\n\n<li><a aria-label=\" (opens in a new tab)\" href=\"https:\/\/httpschecker.net\/\" target=\"_blank\" rel=\"noreferrer noopener\">HTTPS Checker<\/a>. This \u201cfreemium\u201d software, which is available for Windows, Mac, and Ubuntu Linux, is great for\n<ul class=\"wp-block-list\">\n<li>checking for Chrome\u2019s \u2018Not Secure\u2019 warnings, <\/li>\n\n\n\n<li>helping you prepare for an HTTPS migration, <\/li>\n\n\n\n<li>scanning many domains at once, and <\/li>\n\n\n\n<li>checking for issues related to major imports or content changes. <\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><a aria-label=\" (opens in a new tab)\" href=\"https:\/\/github.com\/bramus\/mixed-content-scan\" target=\"_blank\" rel=\"noreferrer noopener\">Mixed Content Scan<\/a>. Found in GitHub, Mixed Content Scan lets you scan your HTTPS website for mixed content. After scanning your site, you\u2019ll see a list of URLs causing mixed content warnings. You\u2019ll see the varied warnings in different colors so you can easily spot what is causing problems on your site. <\/li>\n\n\n\n<li><a aria-label=\" (opens in a new tab)\" href=\"https:\/\/www.jitbit.com\/sslcheck\/\" target=\"_blank\" rel=\"noreferrer noopener\">JitBit Scanner<\/a>: This free tool scans your entire website, even following internal links, to look for insecure images, scripts, and CSS files that trigger mixed content warnings. That said, you can only scan up to 400 web pages with this tool.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"How To Fix Mixed Content Errors On WordPress Tutorial 2020 - How To Fixed Mixed Content Errors\" width=\"960\" height=\"540\" src=\"https:\/\/www.youtube.com\/embed\/0bZvLGdtQdI?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-wrapping-up\">Wrapping\nUp<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the end, <strong>having an HTTPS\nwebsite is more important than ever<\/strong>. Google Chrome will be the first to\ntell site visitors when your site isn\u2019t secure and using an HTTPS connection. Your\nsearch rankings will tank if you have an insecure site, and people will be slow\nto trust your brand or business if you can\u2019t prove to them that they\u2019re safe\nwhile browsing your site.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A free SSL certificate is often <a href=\"https:\/\/www.websitehostingrating.com\/best-web-hosts-with-free-ssl-certificate\/\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\">included in web hosting plans<\/a>, but premium certificates can cost up to hundreds or thousands of dollars. While there\u2019s no one right answer for which type of certificate to choose (because everyone\u2019s needs are different), keep in mind that any free SSL protection is usually domain-validated only (i.e. the least secure option). Here is a <a href=\"https:\/\/www.thesslstore.com\/ssl-compare\/compare-ssl-certificates-prices.aspx\">comparison of SSL certificate<\/a> types to give you an idea of prices, features and level of security offered.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As you can see, <strong>just\nenabling HTTPS on your website isn\u2019t enough<\/strong>. If you have mixed content\nloading over a secure HTTPS connection, you\u2019ll continue to receive mixed or\ninsecure content warnings and push people away. So, take the time to check and\nmonitor your site for insecure content. Because you can bet that even though\nsome site visitors will still risk visiting your site with mixed content\nwarnings, popular browsers like Chrome are going to continue to crack down on\ninsecure sites and prevent users from engaging with them the way you\u2019d like in\nthe future.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Simply supporting HTTPS isn\u2019t always enough \u2014 you also need to know how to identify and fix mixed content errors If you recently migrated your website from an insecure HTTP&#8230;<\/p>\n","protected":false},"author":27,"featured_media":11967,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":"","tve_updated_post":"","tve_custom_css":"","tve_user_custom_css":"","tve_globals":{},"tcb2_ready":0,"tcb_editor_enabled":0,"tve_landing_page":"","_tve_header":"","_tve_footer":""},"categories":[16,10200],"tags":[11679],"class_list":["post-11953","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hashing-out-cyber-security","category-monthly-digest","tag-mixed-content","post-with-tags"],"views":135018,"jetpack_featured_media_url":"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/01\/mixed-content-https.jpg","_links":{"self":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/11953","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/comments?post=11953"}],"version-history":[{"count":0,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/11953\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media\/11967"}],"wp:attachment":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media?parent=11953"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/categories?post=11953"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/tags?post=11953"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}