As you might know, browser’s security model does not allow a script loaded in a page from http://www.example.com to make cross-domain requests (no AJAX calls to any other domain other than http://www.example.com). The Javascript file itself could have been served from a different domain altogether (www.javascript.com/myscript.js) and that is irrelevant. This is the Same-Origin Policy.
Flash also has something similar? But does Flash treat the origin to be the HTML page where the .swf file was loaded or origin is the domain which served the .swf file?
So http://www.example.com loads a .swf file from http://www.swf.com/myflash.swf. Now .swf can load resources only from http://www.example.com or only http://www.swf.com? I’m assuming there are no cross-domain.xml files setup on either example.com or swf.com.
I think, this article explains a lot about the problem you mention: http://www.foregroundsecurity.com/MyBlog/flash-origin-policy-issues.html
From there:
It sounds like if you serve the content from a different domain and there are no cross-domain policy files, then flash cannot access files from your main server.
Also, this article: http://supergeekery.com/index.php/geekblog/2009/12 states that