Search the Community

I have a page that loads 2x iframes, each with a separate adserver zone. If either of the zones contain an ad with a URL target then this is placed in the cookie. When *both* zones contain an ad with a URL, the cookie write is non-deterministic. There appears to be only 1 place in the cookie that the url is written, but I would expect 1 per zone or some other way of differentiating them. Have I done something wrong in configuring the server, if so what? I am using the iframe invocation code (so there are 2x iframes on the page), since - some of my client devices will not support async JS, - I want to install/configure revive centrally (not on 120 webservers) so local mode is out - I do not want to change the many dozens of pages that already embed the iframe & are deployed on the aforesaid webservers. Is this a supported configuration & if not then should I be looking to extend the cookie handling to multiple zones? thanks in advance

I want to limit the number of OAVARS[] being added to a user's cookie. every page refresh adds a new one. What is the best way to prevent this or set a limit? Either prevent it or limit the number (e.g. check during the Max_AddCookie() function)

Hello Revive community, I have found a very weird behavior of Revive adserver 3.0.5. The Adserver works like a charme 99% of the time. But sometimes it happens that no ads are displayed anymore. I could track the issue down to a certain cookie OACBLOCK which is normally only set in combination with a certain campaign ID. But in this rare case the cookie is set without any ID. See the following screenshot of the current cookies in Firefox: If this cookie isset, not a single resource can be loaded from the Adserver. See the following screenshot taken from Firebug. It seems the appearance of this cookie triggers a server error. The error only disappears if the cookie is deleted or the browser is restarted (seems to be a cookie only valid for the current session). Should a file a bug report or does anybody have an explanation for this. The error is relatively rare. I would say once per 1000 page loads but all adds are blocked afterwards which makes the bug a pretty serious one. Thanks for your help Martin