This content has been marked as final. Show 3 replies
He or I should have to post to a wish list to get proper documentation on a security model that's hosed our apps.
your sending swf needs to allow the receiving swf to access data in the sending swf. so, your sending swf needs an allowDomain("receivingSWFdomain") statement.
if your sending swf allows needs something from your receiving swf you'll also need an allowDomain("sendingSWFdomain") statement in your receving swf.
In my case, there was no receiving SWF, only a sending SWF to a serverside page(.php or .asp or something, I don't remember).
I don't even remember what I did to get it to work(my OP was 5 months ago... clearly someone has been searching for answers on Flash security, and, like me 5 months ago, have mostly found unsolved/unhelpful questions :-) )... I think I created a crossdomain.xml file. In the end, everything was deployed on the same domain, I believe the same subdomain as well.
That is still a helpful tip, though... I'll try my best to remember allowDomain() if I ever need cross-domain SWF-to-SWF interaction.