This content has been marked as final. Show 4 replies
The Flash sandbox has become more restrictive as of late. It will only retrieve content from the server it was retrieved from unless there is a crossdomain.xml file at the root of other server allowing access from the original server.
So if you have a http://x.dev.advance.net/crossdomain.xml that allows the y.dev.advance.net server, you should be fine. I think that is how it is done.
There seems to be a few good articles on the subject here:
Thanks for the follow-up.
crossdomain.xml is in place, but the ExternalInterface call raises the sandbox violation, with no sign that it ever attempted to access crossdomain.xml on the external server (x in this case).
crossdomain.xml does seem to work when using URLLoader (something I do later in my script). I see the request in server x's access logs & the script works as expected.
Still researching & looking for definative documentation, but it appears that these two case are different.
Can you try putting the allowScriptAccess directly in the Flex app? And try it with the real domain spec.
Thanks. I've researched this further, and attempted several workarounds, but it seems to the only way
to effect the change I want, is to use the set the allowScriptAccess attribute in the HTML to always.
Since I own the html & flash for this project I don't see this as a problem. But if any one has any more
insight please let me know. Thanks.