( I've previously posted this in the forums, before I new about unityAnswers. Sorry for reposting, but since it didn't attract any views there, I thought maybe I'd try my luck here:) )
The situation is this:
A Unity project is built targeting the WebPlayer platform. The resulting .html and .unity3d files are put in Apache's htdocs, and served by the localhost. The project, when launched by loading the page http://localhost/WebPlayer.html, tries to connect to a server application, which is also running on localhost.
Since both the Unity client and the server reside on the same domain, I expected there would be no need for a crossdomain.xml, but I still get the "Unable to connect, as no valid crossdomain policy was found". (Of course, if I launch the Unity's pre-packaged policy server, there is no problem).
Running from within the Unity Editor, with "WWW Security Emulation Settings" set to http://127.0.0.1/WebPlayer.unity3d has the same result.
The question is, should this be happening? (I think it shouldn't.) Why is Unity trying to get a crossdomain policy in this case? Am I missing something?
Any info would be appreciated.
↧