This content has been marked as final. Show 4 replies
Wondering if you found a fix for this problem? I'm having the same problem in Flex 3 on Flash Player 10.
Yes I did. The problem is caused due to new security restrictions that were added to the Flash 9.0.124 release. In older versions of the flash player, the security constraints were not as strict as versions 9.0.124 and after. There are a couple ways to solve this issue with the easiest being a modification to your crossdomain.xml file if you have access to it. There is a good article on the changes at http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security.html. The crossdomain file specification can be viewed at http://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html.
An older crossdomain.xml looks similar to:
<!DOCTYPE cross-domain-policy SYSTEM " http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<allow-access-from domain="www.yoursite.com" />
<allow-access-from domain="yoursite.com" />
The newer way of writing your crossdomain.xml looks like:
<!DOCTYPE cross-domain-policy SYSTEM
<allow-http-request-headers-from domain="*" headers="SOAPAction"/>
and as you can tell there are more tags needed to allow flash to access the content.
Outside of using a crossdomain.xml, you can explicitly define your flash player security within your flex application using the Security class in the following format:
The reference to the Security class can be found at http://livedocs.adobe.com/flex/3/langref/flash/system/Security.html and i will leave it to you to determine which of these methods fits your needs best.
Hope this has provided some help.
Should read :
Thank you Shawn! While it wasn't my exact problem, it actually pointed me in the right direction. I actually needed to move the instantiation of my URLRequest and FileReference classes into the constructor method of my class. I explain more detail about the problem in my blog.