Problem
This error occurs when connecting on your browser with HTTPS and the padlock is not locked and crossed out in red.
"Your connection to www.domain.com is encryped with 256-bit encryption. However, this page included other resources which are not secure."
Cause
You are using non-secure Frames or other content, which reside on a nonsecure "http" directory usually on your server. So, the lock will not be shown with an "https" session with the insecure frames even if the page is secure (Browser bug).
Resolution
In order to resolve your problem please perform the steps below:
1. Please ensure you are accessing your frame (if frames are being used) and all other content via "https". If you reference the frame using non-secure "http" as the browser checks, the padlock will not display. With this process you can make sure that all the content displayed on the page come from a secure location.
2. You can decide not to use frames or source the frames from the domains main directory on your server. If you want to display the padlock on your secure page, you can also check that any images or banners are being sourced from your secure directory. Afterwards, this enables you to reference all your pages through "https" without the warning prompt.
3. You need to put your media files in a secure directory.
If you are using ASP pages with "include file" using headers and footers and no frames please read the following solution on how to force SSL on ASP pages, click here
Try adding a URL base to the <head> section so that the relative links can be referenced as absolute and secure paths.
For example:
<head> <base href= "https://www.ssl247.com/"> </head>
This tag needs to be placed in the individual pages and not within <frameset> or <frame src > tags