Problems with VASTAdTagUri

552 views
Skip to first unread message

Juan Ignacio

unread,
Jul 4, 2014, 6:02:08 AM7/4/14
to ima...@googlegroups.com
Hi,
  First all, my name is Juan Ignacio from Spain and I'm working with Kaltura platform. We use Flash SDK, and the problem is that some adServers send us malformed VAST XML. They include a white space in the value of VASTAdTagURI label after "CDATA[ http:" and caused an error and not serving de advertising. Example: 

"<?xml version="1.0" encoding="utf-8"?>
<VAST version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="vast.xsd">
    <Ad id="237863124">
        <Wrapper>
            <AdSystem version="2.0">XXX</AdSystem>
            <VASTAdTagURI><![CDATA[ http:// "......

......

instead of:

"<?xml version="1.0" encoding="utf-8"?>
<VAST version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="vast.xsd">
    <Ad id="237863124">
        <Wrapper>
            <AdSystem version="2.0">ANA</AdSystem>
            <VASTAdTagURI><![CDATA[http://"....

it can be test in Vast Inspector Tool.

Can we do anything to "sanitize" de label <VASTAdTagURI> in the player?

Thank you very much.

Best Regards,

Bret McGowen

unread,
Jul 7, 2014, 6:36:26 PM7/7/14
to ima...@googlegroups.com
Hi Juan,

Thanks for your suggestion. Right now the SDK won't automatically strip out the preceding whitespace but I'll take the issue to the team and update this thread if we come up with anything.

Cheers,
Bret McGowen
IMA SDK Team

Bret McGowen

unread,
Jul 9, 2014, 4:47:50 PM7/9/14
to ima...@googlegroups.com
Hi Juan,

Is this something that you can get resolved by the ad server? They shouldn't be sending a URL with a preceding space anyway.

Thanks,

Juan Ignacio

unread,
Jul 10, 2014, 3:29:48 AM7/10/14
to ima...@googlegroups.com
Hi Bret,
  First of all thank you very much for your answers. We can't solve the problem in the ad server because is a third party server and is not the only one that have this problem, we detect at least three and we fear might happen in some more in the future.

  We know that is something unnecesary "sanitize" the field, because is not a valid XML, but is something that we find and we need to solve it. We try to solve it by storing the first XML, do the sanitize,  and use this new XML using the method "adsResponse" of the "AdsRequest" class, but we noticed that the problem can manifest in the second or third wrapper.

Thanks for all of your interest.

Best regards,
Juan

Bret McGowen

unread,
Jul 10, 2014, 5:35:45 PM7/10/14
to ima...@googlegroups.com
Hi Juan,

Thanks for letting us know -- you're right that sanitizing yourself would only work for the first VAST request. I'll take this request to the team and let you know if we are able to implement it.

Cheers,
Reply all
Reply to author
Forward
0 new messages