Cross URL ArcGIS Server

NicholasGosselin

We are developing a Silverlight product where by default we use the Bing imagery, but optionally, clients can utilize their own ArcGIS Server services.  I am aware that this requires having either the "clientaccesspolicy.xml" or "crossdomain.xml" files.  Currently, we have created a crossdomain.xml that is WIDE open for testing purposes.

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
    <site-control permitted-cross-domain-policies="all"/>
    <allow-access-from domain="*"/>
</cross-domain-policy>

The issue we are seeing, is that when the Silverlight application is hosted from http://admin.aaaaa.com and the ArcGIS Server is located at http://something.bbbbb.com we notice that the ESRI out of the box legend properly shows all the layers for the service in addition to the extents they are enabled.  The problem is that once we zoom into the extent that service should be showing data for (ie. the layers should be visible & the legend acknowledges this too), the map data never shows up.  I used Fiddler, and found that the point in which the data was available for the current extent, there was no HTTP request to the ArcGIS Server service.  When I open the ESRI legend, I see the HTTP request to the ArcGIS Service.  Everything works properly when running it from my developer environment.

My question is, what else am I missing that would cause ArcGIS Service data to not be loaded on the map?

EDIT: I should note that the URL we are using is utilizing SSL and our ArcGIS Service is not using SSL.  In addition, I discovered that a FeatureServer that an employee created through ArcGIS Online DOES work with our application, but the ESRI World Streets Basemap does not.

DominiqueBroux

I should note that the URL we are using is utilizing SSL and our ArcGIS Service is not using SSL.

Cross domain support over SSL needs to be explicetly authorized in the ClientAccessPolicy file:

<access-policy>
 <cross-domain-access>

<policy>
 <allow-from http-request-headers="*">
 <domain uri="http://*"/>
<domain uri="https://*"/>
 </allow-from>
 <grant-to>
 <resource path="/" include-subpaths="true"/>
 </grant-to>
 </policy>

</cross-domain-access>
 </access-policy>

Not sure of the syntax with CrossDomain but I guess there is something similar.