flyfishtom

Andrew id the Revive server setting credentials to true, possibly for setting a cookie ? Also, nowhere on my Apache Revive server or my Apache web server am I setting Access-Control-Allow-Origin to "*" so I'm curious if Revive is doing this. As a result of this I am not able to get Banner Delivery Capping to work. I can enter the caps in the UI but the ads don't play once I set the caps. I think the cookies aren't working. When I set the Campaign to "Show capped ads if cookies are disabled " the ad plays but it doesn't use the caps I set, it plays every time. Tom https://github.com/whatwg/fetch/issues/251 .

Is anyone successfully using Amazon S3 and Cloudfront to serve ad content? I am able to access my content directly via Cloudfront but when I use the Cloudfront distribution url in Revive the content does not appear. If I use the S3 url (without using cloudfront) the content serves up fine. Does anyone have Cloudfront working with Revive? Tom

Sorry for the delay. Yes it's a third party vast 3.0 plugin. I'll follow up with the developer. Thanks for looking at it. Tom

were you able to figure this out?

Has anyone seen this error before? Is there a setting in Revive Adserver to fix this? It seems to be coming from revive code. XMLHttpRequest cannot load http://52.1.183.40/adserver/www/delivery/fc.php?script=bannerTypeHtml:vastI…3D3&nz=1&source=&r=R0.05822725687175989&block=1&format=vast3&charset=UTF-8. A wildcard '*' cannot be used in the 'Access-Control-Allow-Origin' header when the credentials flag is true. Origin 'http://www.megabitllc.com' is therefore not allowed access. The credentials mode of an XMLHttpRequest is controlled by the withCredentials attribute.

Hi, I am having a problem with CORS. When I test my server URL I get success. http://www.test-cors.org/#?client_method=GET&client_credentials=false&server_url=http%3A%2F%2F52.1.183.40&server_enable=true&server_status=200&server_credentials=false&server_tabs=remote When I test past the server URL I get fail. http://www.test-cors.org/#?client_method=GET&client_credentials=false&server_url=http%3A%2F%2F52.1.183.40%2Fadserver%2Fwww%2Fdelivery%2Fasyncjs.php&server_enable=true&server_status=200&server_credentials=false&server_tabs=remote http://www.test-cors.org/#?client_method=GET&client_credentials=false&server_url=http%3A%2F%2F52.1.183.40%2Fadserver&server_enable=true&server_status=200&server_credentials=false&server_tabs=remote Does the adserver have any unique cors settings? Tom

Is it possible to serve a pre roll video ad to an Android browser (chrome) and iOS browser (safari) using one of the third party VAST plugins?

I just found and replied to your email. Thanks for that. Tom

Hi I filled out the form on Tuesday. Please take a look at your convenience. Tom

Erik, How do I go about contacting you regarding the Vast 2.0 plugin?

After a day's worth of effort I've learned that this software does not support VAST 2.0 for video ads. :( .

The cookie issue was resolved by the time zone being corrected. I'm assuming the cookie is time sensitive. Just documenting my steps for some other newbie that stumbles across these similar errors. Tom

I eliminated the timezone error by adding this to line 2 of the variables.php file. (I am using UTC) date_default_timezone_set('UTC');

now I've got the timezone error and the cookie error upon attempting to log in. It seems that these are common errors so I am researching online....

OK problem solved. I am running Centos 7 and selinux was enabled. I disabled selinux and it I no longer get the permission errors.