locked
ClientAccessPolicy issue... I think. RRS feed

  • Question

  • Fisrt of all I have my ClientAccessPolicy.xml file in the root of my website.

    If I access my website using the public domain name like this:
    http://www.mydomain.com
    and then go to the page where my SL control is, I get the spinning % numbers up until about 98%, then it quits and my SL control does not appear on the page.

    If I access my website using the machine name (website is at datacenter, we have vpn setup) like this:
    http://machinename
    and then go to the page where my SL control is everything works fine.

    The xap file has a ServiceReferences.ClientConfig that points to http://mydomain.com/myservice/myservice.svc

    this must be a ClientAccess Policy issue don't your think?  Or what DO you thnik the issue is? 

    Thanks in advance.

    Here is the contents of my ClientAccessPolicy.xml file:

    <?xml version="1.0" encoding="utf-8" ?>
    <access-policy>
    <cross-domain-access>
    <policy>
    <allow-from http-request-headers="*">
    <domain uri="*" />
    </allow-from>
    <grant-to>
    <resource path="/" include-subpaths="true" />
    </grant-to>
    </policy>
    </cross-domain-access>
    </access-policy>

    Thursday, March 18, 2010 4:23 PM

All replies

  • I doubt it's cause. Use fiddler monitor the wire, is there any service call when your control initialize?

    And if you change a machine will this happen?

    Since your xap can be downloaded and to 98%, also if there is no service call when initializing.

    I suspect it's a client enviroment issue.

    Sunday, March 21, 2010 10:38 PM