Maro Posted June 3, 2018 Report Share Posted June 3, 2018 Hello everybody. I want to serve video ads and i get this error: Failed to load https://adserver.tld/www/delivery/fc.php?script=bannerTypeHtml:vastInlineBannerTypeHtml:vastInlineHtml&format=vast&nz=1&zones=pre-roll%3D8: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'https://imasdk.googleapis.com' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute. It's similar to the html5 banner error from version 4.1.1, that was fixed through update. I want to show the video ad in a wordpress website with foliovision's fv player plugin and their VAST plugin. Is here anyone who know how to fix this? Thank you in advance Maro Quote Link to comment Share on other sites More sharing options...
Maro Posted June 5, 2018 Author Report Share Posted June 5, 2018 The Revive Version is 4.1.4. Please help :( Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted June 6, 2018 Report Share Posted June 6, 2018 Does this help? https://documentation.revive-adserver.com/display/DOCS/Server+Cross+Domain+Policy Quote Link to comment Share on other sites More sharing options...
Maro Posted June 7, 2018 Author Report Share Posted June 7, 2018 Hi, thank you! „This only applies to Flash-based video players. HTML5 video players do not require any crossdomain.xml policy file configuration.“ I already read this, but it seems to be only necessary for flash videos. I want to use only html5 videos. Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted June 12, 2018 Report Share Posted June 12, 2018 Well, the error you are seeing seems pretty clear: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'https://imasdk.googleapis.com' is therefore not allowed access. Seems like setting something other than the wildcard might help? Quote Link to comment Share on other sites More sharing options...
Maro Posted June 12, 2018 Author Report Share Posted June 12, 2018 8 minutes ago, andrewatfornax said: Well, the error you are seeing seems pretty clear: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'https://imasdk.googleapis.com' is therefore not allowed access. Seems like setting something other than the wildcard might help? I use Plesk server administration software. I can add additional headers but then it shows the error, that there are more than one directives. I dont know what this googleapi is, but if revive need this connection, than is the asterisk the right configuration, no? Quote Link to comment Share on other sites More sharing options...
Maro Posted June 14, 2018 Author Report Share Posted June 14, 2018 Which credentials? What means include? Where to change it? Quote Link to comment Share on other sites More sharing options...
Maro Posted June 14, 2018 Author Report Share Posted June 14, 2018 i tried this: https://developers.google.com/interactive-media-ads/docs/sdks/html5/cors but itis already true, so: "The value of the 'Access-Control-Allow-Credentials' header in the response is 'true, true which must be 'true' when the request's credentials mode is 'include'. Origin 'https://thevideowebsitethatshouldshowthevideo.com' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute." Quote Link to comment Share on other sites More sharing options...
Maro Posted June 14, 2018 Author Report Share Posted June 14, 2018 Did anyone know another good adserver software? I have not to be free.... It should just work. Quote Link to comment Share on other sites More sharing options...
Maro Posted June 22, 2018 Author Report Share Posted June 22, 2018 Is there nobody who has the same issues? Really? Quote Link to comment Share on other sites More sharing options...
Maro Posted June 22, 2018 Author Report Share Posted June 22, 2018 This is seen at the foliovision vast tester https://foliovision.com/player/vast/tester FV VAST load (0,html5) https://servingdomain/www/delivery/fc.php?script=bannerTypeHtml:vastInlineBannerTypeHtml:vastInlineHtml&format=vast&nz=1&zones=pre-roll%3D8 fv-player-vast.min.js?ver=6.6.2.1:1 FV VAST Ads init. fv-player-vast.min.js?ver=6.6.2.1:1 FV VAST Ad error: AdError 1010: The ad response was not understood and cannot be parsed. After reload the CORS message is there again: Failed to load https://servingdomain/www/delivery/fc.php?script=bannerTypeHtml:vastInlineBannerTypeHtml:vastInlineHtml&format=vast&nz=1&zones=pre-roll%3D8: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'https://imasdk.googleapis.com' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute. Quote Link to comment Share on other sites More sharing options...
Maro Posted September 5, 2018 Author Report Share Posted September 5, 2018 Anyone a clue? ?? Quote Link to comment Share on other sites More sharing options...
Maro Posted September 16, 2018 Author Report Share Posted September 16, 2018 It seems to be gone, at this time there is no CORS Error. With foliovision VAST Tester, i got this next error: FV VAST Ad error: AdError 1010: The ad response was not understood and cannot be parsed. Maybe the player doesn't support this Version of VAST? I also tried to use = instead of %3D after "...pre-roll..." Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.