Occasionally you may get a notice from a browser or company that your site has insecure pages due to a
"mixed content" problem. This is when you have referenced an element using insecure transmission, such as a 3rd party snippet, an image or such that is using HTTP:// rather than HTTPS://
The quickest steps to resolve the issue are to identify the insecure reference, then track it down in your site and change it to HTTPS:// . If it cannot be delivered securely, then you need to either omit it, or find another means to add it to your site such as copying it to your local site folders where it can be referenced securely.
- Open the site in a browser such as Chrome or Firefox and browse to a page that is insecure with the mixed content warning. You will note that the browser displays the page as insecure to the left of the URL in the address bar: Firefox exampleChrome example
- RIGHT-CLICK on a blank area of the page and choose View Page Source .
- In the resulting page that is displayed, pull up the Find bar by clicking Ctrl+F
- Search for the text: http:
- Click through all instances of http:// references in the Find tool, and note each one.
NOTE: You can generally ignore <a href="http://..."> types, as those are hyperlinks to other pages, rather than displayed content that causes mixed content warnings.
- Copy/Paste any http:// URLs that may be mixed content references to a Notepad text file. An example would be something like:
- Note any tell-tale context around the references that might tell you where it is in your site, such as: header , footer , or other useful keywords.
- For may sites, these references are created in TOPIC pages, so access your site admin and go to Content - Manage Topics.
- In the Topic Description filter, search for the errant references, such as: http:// mysite.com/Images/mrfixit.jpg , and identify any topics that contain the insecure references.
- Edit each Topic for the reference to be https:// and Save
- Refresh Store and browse to the insecure pages again to see if you have successfully edited the problem.
NOTE If you cannot identify the source of the insecure reference, please contact the Vortx Help Desk to assist, or your developer if not hosted with Vortx.