Shulou(Shulou.com)06/02 Report--

This article mainly shows you "how to solve the Flex security sandbox problem", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "how to solve the Flex security sandbox problem" this article.

Solution to the problem of Flex Security Sandbox

On the solution of the Flex security sandbox problem a few days ago, I made a Flex Mini Program to update the data by visiting the xml of the front end of the service. There is no problem in debugging and calling the local xml file. When the url is changed to the server, there is SecurityError. Through the Internet search, it is concluded that it is the problem of the Flex security sandbox. The following is the way to solve the Flex security sandbox problem found on the Internet, for reference only.

Method 1:

Deploying the crossdomain.xml file on the target server (this method I use works well, I can put it on it) requires that the remote service root directory is defined with a crossdomain.xml file, as follows:

Method 2:

Using an agent, the remote files to be accessed by Flex are read locally through scripts such as asp,php,jsp, and then accessed by Flex

Method 3:

The fifth way to solve the Flex security sandbox is to use Adobeflashplayer9 to open the program, click File in the menu bar-> create player. The exe file is generated, and the security limit can be broken by running the exe file.

Method 4:

1. Find this folder: C:\ DocumentsandSettings\\ ApplicationData\ Macromedia\ FlashPlayer\ # Security

2. Create a folder called "FlashPlayerTrust" under it

3. Create a new TXT file under the "FlashPlayerTrust" folder as follows: C:\ d:\ e:\ f:\

4. Name the txt file "myTrustFiles.cfg" and then open the SWF file on your hard drive, and the annoying security settings prompt window will not appear!

Method 5:

The fifth way to solve the Flex security sandbox is to use HttpService, which has Proxy by default and needs to be configured with flex-config.xml, which contains a paragraph: …

This is a whitelist and is generally commented out, that is, only local http://{localserver}/* and https://{localserver}/* can be accessed by default. Others need to be modified to what they need in flex-config.xml.

Naturally, visiting the local area will not cross-domain, but you must have access to other machines in the local area network, so it belongs to cross-domain according to the whitelist rule.

The above is all the contents of the article "how to solve the Flex security sandbox problem". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.