Apparently because I am new here I cannot even post sufficent links to explain my problem fully. FYI
Source
mp4stream.com / preroll / videe /
This is one of many demos I have setup for various Ad Networks. Almost all have the same result.
Part One
A lot of the Ad Networks I demo all have the same issue that looks something like this. I'm talking at least 10 partners I've tested have. Below is an example of one.
XMLHttpRequest cannot load http://vast.videe.tv/vast-proxy/?VPAID=1&aid=12988&sid=0&channel_id=0&conte…player_width=657&player_height=370&vid_duration=1440&cb=685997865628451100. A wildcard '' cannot be used in the 'Access-Control-Allow-Origin' header when the credentials flag is true. Origin 'http://mp4stream.com' is therefore not allowed access.*
These failures create a huge increase load time and affects the entire player / user experience as a whole.
One Ad Network today indicated that I may be passing cookies to them and that is why the above is failing. But I have a hard time believing that based on my development / server experience. As far as I'm aware every single player JWplayer or otherwise would use cookies of some kind.
So the question I have is why do hundreds of these simply fail?
to be servable in a JavaScript environment a VAST ad server’s response must include the following HTTP CORS headers:
Access-Control-Allow-Origin:
Access-Control-Allow-Credentials: true
This HTTP header allows an ads player on any origin to read the VAST response from the ad server origin. The value of Access-Control-Allow-Origin: should be the value of the Origin header sent with the ad request. The Access-Control-Allow-Credentials: header will ensure that cookies will be sent and received properly.
Hope this helps...