I hate digging up old threads, but this was linked as a top google search for the problem.
I too, have a similar issue, and i have been trying to find a solution: I can describe my case with more detail - but i am hesitant to post code that has not been sanitized, due to content.
I am a publisher who uses revive to serve other peoples ads on my sites. My revive cluster runs both http and https (with valid ssl certs), with both protocols using the same docroots, etc.
The delivery looks something like this:
My site -> My Revive Iframe invocation -> My revive HTML banner -> client iframe source -> Client banner
If i directly call one of my ads via http and https, the ads are delivered as expected:
My site (http) -> My Revive Iframe invocation (http) -> My revive HTML banner -> client iframe source (http) -> Client banner
If i move everything except my revive invocation to https, everything works:
My site (https) -> My Revive Iframe invocation (http) -> My revive HTML banner -> client iframe source (https) -> Client banner
If i call the client iframe via http, and my revive via https, everything works:
My site (https) -> My Revive Iframe invocation (https) -> My revive HTML banner -> client iframe source (http) -> Client banner
However, as soon as i make my revive invocation https, and the clients' iframe src https, revive delivers blanks in the body.
My site (https) -> My Revive Iframe invocation (https) -> My revive HTML banner -> client iframe source (https) -> Client banner
<title>Advertisement</title>
<style type='text/css'>
body {margin:0; height:100%; background-color:transparent; width:100%; text-align:center;}
</style>
</head>
<body>
</body>
</html>
