We're using PlayFab with Unity3D 4.7.2 for the WebPlayer target. Due to the sandboxing of the WebPlayer target, it requires a `crossdomain.xml` from the host that you're trying to fetch from. Now the API works fine, but when we try to download from the CDN ( `https://cdn.playfab.com` ) it also tries to fetch a `crossdomain.xml` at the root of that address, and since there isn't one, it fails. That leaves us unable to download from the CDN on the WebPlayer target.
Starting a new Answer for clarity. As you'll see, the crossdomain.xml is now being returned by our Content service. Whether you're using Starling, Unity WebPlayer, or anything else that requires it, please give it a shot and let us know if you're still seeing any issues. With WebPlayer, please bear in mind that setup of your own hosting box (local or otherwise) can be a bit tricky - we'll have a post soon from our tools team to talk about that more.
We've updated our CloudFront configuration to enable WebPlayer. Can you please confirm if this is now working for you?
Nothing has changed on our side. When Unity WWW tries to fetch the "crossdomain.xml" from the root of the download URL ( https://cdn.playfab.com/XXX/... ) it still fails. I checked manually and all requests for "https://cdn.playfab.com/crossdomain.xml" still result in a 403.
Hi, when i try to download file from https://cdn.playfab.com/XXX i got Security sandbox violation (AS3)
and https://cdn.playfab.com/crossdomain.xml it's not present.
Still not able to download files from the content server:
Rejected because no crossdomain.xml policy file was found
Could you please get a Wireshark or Netmon capture of this, and send it to us at devrel@playfab.com, so that we can review the specifics of what you're seeing?
A network capture won't do much good since it's an encrypted connection. But a simple browser request to the URL ( https://cdn.playfab.com/crossdomain.xml ) will yield 403, it should be the same request the WebPlayer is trying to send. We did do a capture, and the only crossdomain.xml traffic we could see that wasn't encrypted, was to GameAnalyicts which sends it's pings over an unencrypted connection so we could see the initial request for the file.
Actually, one other question, since you're specifically using the WebPlayer sandbox: you do have a crossdomain.xml at your own domain, correct (http://yourdomain/crossdomain.xml)?
1 Person is following this question.
