This project is read-only.

Force user agent string for VAST requests in AdSchedulerPlugin/AdHandlerPlugin

Topics: Windows 8 Xaml
Oct 9, 2012 at 3:52 PM

When scheduling VAST Uris in the AdSchedulerPlugin that poll FreeWheel servers, the FreeWheel server is requiring a user agent header in order to respond with a valid response.  The player framework doesn't send a user agent in the header.

VAST requests without User Agents result in a 403 Forbidden from the FreeWheel server.  How would I go about setting/forcing a User Agent header for VAST requests?


GET;;ptgt=a&slau=PREROLL&slid=mobile_383118_0 HTTP/1.1

HTTP/1.1 403 Forbidden
Content-Length: 0
Date: Fri, 05 Oct 2012 22:37:45 GMT
Server: FWS
Set-Cookie: NSC_mpobewjq1.gxnsn.ofu=ffffffff09095e3b45525d5f4f58455e445a4a423209;path=/;httponly 

The same Uri sent from a web browser (with browser's user agent header) yields the appropriate XML response.  FreeWheel verifies that they require a User Agent header that matches a whitelist they maintain which matches the whitelist maintained by the IAB.  FreeWheel suggests using the IE 10 User Agent string "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0)" for windows 8 developers.


Oct 10, 2012 at 11:13 PM

Rob, thanks for reporting this. We're working on an update now that will include the useragent with FreeWheel requests. This will be available in the next public release currently targeted for 10/26. Please DM me if this is a blocking issue and you need this change sooner.