MIxed context

[cubells]

Hi all there.

I have a problem on my web.

I get an error on all browsers saying context was blocked because ads are serving mixed content.

The insecure url is http://myserver.org/www/delivery/fl.js

In the banners, the script has a correct url:

https://myserver.org/www/delivery/spcjs.php?id=1

but revive adserver serves really the insecure url.

All the settings (requireSSL=1) seems to be correct.

I've read the documentation and a lot of messages on forum and it seems to be a revive problem.

 

How can I solve that problem in order to avoid error messages?  Is it a ssl configuration error?

Thanks a lot!

Edited August 30, 2015 by cubells

[AntiMozg]

I'm sorry for digging this thread out, but is there were a solution to the problem?

I have the same issue using async code on the website pages after moving from http to https. Revive loaded from http, content marked as mixed and nothing seems to be helping.

[SLSHOP]

The Browser is reporting a false positive... The issue actually relates to the "Minimum TLS Version", if your banner server support TLS 1.0 this deprecated in modern browsers and will report as not secure appearing as content was included over http as opposed to https.

Having spent sometime with this issue I can confirm I was able to resolve the problem.

In the first instance I updated the URL for fl.js to it's full https url via Banner Delivery Settings > Delivery File Names: 

Flash Include (Can be a full URL)

With the above in place we changed the minimum TLS supported by the server to TLS 1.1

This resolved the mixed content warning.

Hope this helps someone.

Thanks Laurie