Jump to content
jmblasco

Serving Ads Over Https Fails

Recommended Posts

Afther installation it works fine.

 

But, if we use  https:// ....    no banners are served. Why?

 

We cann't find any solution (we tested everything we know about configuration).

 

Does anybody can help me?

 

 

Environment:    Apache 2.2.2  + php 5.3.10  + postgresql 9.1 + Revive 3.0.2

 

 

Share this post


Link to post
Share on other sites

Can you please provide a lot more information? Like for example - what tag type you are using? Where we can see the generated invocation tag in raw form? Where we can see the tag working on a non-SSL site, and not working on an SSL enabled site?

 

Thanks.

Share this post


Link to post
Share on other sites

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>

 

Share this post


Link to post
Share on other sites

I am having this problem also. 

 

Both the ad-server and the website these ads are being served on are running HTTPS. However once the first script is invoked it seems to be pulling the remaining files via non-SSL. I get these type of errors when I inspect element:

...was loaded over HTTPS, but displayed insecure content from 'http://example.com/www/delivery/lg.php?bannerid=4.....

Even though my embed code looks like this:

<iframe id='a4d58c4e' name='a4d58c4e' src='https://example.com/www/delivery/afr.php?refresh=10&amp;zoneid=1&amp;cb=INSERT_RANDOM_NUMBER_HERE' frameborder='0' scrolling='no' width='100%' height='250' allowtransparency='true'><a href='https://example.com/www/delivery/ck.php?n=aefcd416&amp;cb=INSERT_RANDOM_NUMBER_HERE' target='_blank'><img src='https://example.com/www/delivery/avw.php?zoneid=1&amp;cb=INSERT_RANDOM_NUMBER_HERE&amp;n=aefcd416' border='0' alt='' /></a></iframe>

As far as I can tell the auto-generated files in www/delivery/ are not properly switching to the SSL url. I can't figure out how to force SSL with out manually editing these files. Any ideas are welcome.

Share this post


Link to post
Share on other sites

We are using zone level tags succefully usingn HTTPS. We have installaed all ther certificates correctly. Before getting a brand new SSL cert, we first tried with test cert and used it on both mobile and desktop.

 

On the tags side we changed everythign to SSL.

 

Rememeber that for SSL ensure to test across browers, devices and OS to be sure.

 

Thanks!

Aditya

Share this post


Link to post
Share on other sites

Another installation suffering this problem here.

Using the JS invocation code. Code runs on page and requests add from

http://domain.com/revive/www/delivery/ajs.php?zoneid=2&charset=UTF-8&cb=123123123&charset=UTF-8&loc=http%3A//otherdomain.com/path/page.php

works just fine.

Make the URL https and it claims it can't find an ad to serve. The OX_random string is set just fine, and with 3.1 the beacon is served, but no ad.

Oddly though, if I change the zoneid to another valid zone, it DOES seem to serve under SSL just fine. Is there a setting regarding https delivery I'm not seeing?

Share this post


Link to post
Share on other sites

Well, I have no idea how it fixed, but after multiple delivery_cache* resets and running through all the campaign & banner settings screens checking all settings against zones that appeared to be working, it started working. Nothing was changed. Can only guess some new setting since the upgrade from 3.0.0 was reset by saving a page of settings somewhere.

Share this post


Link to post
Share on other sites

Another installation suffering this problem here.

Using the JS invocation code. Code runs on page and requests add from

http://domain.com/revive/www/delivery/ajs.php?zoneid=2&charset=UTF-8&cb=123123123&charset=UTF-8&loc=http%3A//otherdomain.com/path/page.php

works just fine.

Make the URL https and it claims it can't find an ad to serve. The OX_random string is set just fine, and with 3.1 the beacon is served, but no ad.

Oddly though, if I change the zoneid to another valid zone, it DOES seem to serve under SSL just fine. Is there a setting regarding https delivery I'm not seeing?

 

If you have HTML banners containing http:// urls, then Revive Adserver won't serve them over SSL to avoid browser error messages. Please fix your banners, wait for the delivery cache to expire (or clean it up manually), then retry.

Share this post


Link to post
Share on other sites

Aha, that was exactly it, thank you! The one tweak I made in all the re-saving was making the third party ad code https.

An excellent feature, but that one requires documentation. Ideally I'd put a warning right on the page when you save your ad code, if you detect insecure code.

Share this post


Link to post
Share on other sites

Had exactly the same problem.

In the end the problem was that if you supply an HTML banner, and the zone is rendered under SSL, Revive performs a check if there is any SSL-unsafe code in the banner. If it does detect that kind of code, the the banner is simply not delivered.

In my case, I have added banner with the following type of code: <iframe src=http://...></iframe>
The snippet that loaded from SSL URL of Revive did not serve that banner, while non-SSL version of snippet did.

Share this post


Link to post
Share on other sites

Hi there,

we got exactly the same problem.

We just move our AdServer to HTTPS, everything works fine, EXCEPT :

- HTML5 banner added with iframe.

  • Invocation code (Iframe) called from HTTP works perfectly
  • Invocation code (iframe) called from HTTPS does not deliver anything... the body in the source code is empty.
  • Invocation code (JS) called from HTTP works perfectly
  • Invocation code (JL) called from HTTPS does not deliver anything... the body in the source code is empty.

Has anybody been able to solve this problem ? We tried all solution and combinations.... :(

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×