Why is our RescueGroups.org website not displaying the HTTPS padlock?

1 answer

1.  

   1

   0

   -1

   • Emily T [RG]
   • Nov 16, 2020

   The most common reason for this issue is that your website contains mixed content. Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display on the same webpage, while the initial request was secure over HTTPS.

   For our users, the vast majority of mixed content errors occur when they link to an image on another site using HTTP instead of HTTPS. Using the insecure HTTP protocol in this way weakens the security of the entire page, and displays warnings to indicate to website visitors that your site contains insecure resources. It is highly recommended that you avoid the use of HTTP links.

   One common example is that our organizations will use a HTTP link to a badge on Adopt-a-Pet.com. Most websites that provide badges make them available over both HTTP and HTTPS, including Adopt-a-Pet.com. This means you can still use the Adopt-a-Pet badge, but you should make sure the link and the image source starts with HTTPS. So, you would want the HTML to read:

   <a href="https://www.adoptapet.com" target="_blank">
   <img src="https://images.adoptapet.com/images/shelter-badges/Approved-Shelter_Blue-Badge.png">
   </a>
   
   

   instead of the default:

   <a href="http://www.adoptapet.com" target="_blank">
   <img src="http://images.adoptapet.com/images/shelter-badges/Approved-Shelter_Blue-Badge.png">
   </a>
   
   

   •  Comment

   CommentAdd your comment...