Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Regarding crossdomain.xml

Hi,

We are using JWPlayer to serve video ads to our partner sites.

I found there are two calls made to our server, GET https://embed.insticator.com/crossdomain.xml 404 (Not Found) and GET http://embed.insticator.com/embeds/videoAd?busted=9850 400 (Bad Request).

I took a look at this article, http://support.jwplayer.com/customer/portal/articles/1403679-crossdomain-file-loading
I am still confused about it, should I create a crossdomain.xml file and include all the partner sites we are serving ads to?

How about the second request? It add the parameter busted and since it doesn't provide required parameter, server returns a 400. What is that call about?

Thanks,
Tianyi

1 Community Answers

Up Down

Randy

JW Player Support Agent  
0 rated :

Hello Tianyi,

The crossdomain.xml file will enable access for external websites to your web server resources. By default, this feature is turned off for security reasons. You would place the sites that require access into the xml like so:

RESTRICTED ACCESS

<?xml version=“1.0”?>
<!DOCTYPE cross-domain-policy SYSTEM “http://www.adobe.com/xml/dtds/cross-domain-policy.dtd”>
<cross-domain-policy>
<allow-access-from domain="*.domain1.com"/>
<allow-access-from domain="www.domain2.com"/>

</cross-domain-policy>

ALLOW ALL

<?xml version=“1.0”?>
<!DOCTYPE cross-domain-policy SYSTEM “http://www.adobe.com/xml/dtds/cross-domain-policy.dtd”>
<cross-domain-policy>
<allow-access-from domain="*" />

</cross-domain-policy>

The crossdomain.xml needs to reside in the root of the web host. Lets see if this resolves the Ad error as well.

Randy

This question has received the maximum number of answers.