juice-project.org

One of the issues new users of Juice come up against is the problem of mixed content warnings. This is usually in a situation where Juice is running on a system that has both secure and insecure versions, one for people accessing their accounts, one for people just browsing. These warnings are caused by having both secure (https) and insecure (http) resources on the same page.

In this situation, the warnings are most likely caused by using the Google API based extensions or other external resources loaded from non-secure locations into a secure page.

The easiest way to handle this is to detect the type of page being used and branch your Juice extensions accordingly. In Juice 0.7 we fixed the loading of Google APIS to always match the document's level of security, and we also provide a quick way to check with with the $.juice.protocol:

if($.juice.protocol!='https://'){
    //put code that should only run on insecure pages here
}

In older versions of Juice you can use:

if(document.location.protocol!="https:"){
    //put code that should only run on insecure pages here
}