Have Geek Brain

Breaking sandbox security when connecting to Socket from flex

I am using a Socket (not xmlSocket) connection between flex apps and messages pushing the server.

Now when I connect from the local machine to the server everything is up and running, the connection is successful and I get the data back and forth.

When I upload the application (flex) to the server and run it from there, I get a sandBox security breach message.

Note: 1. I have a wildcard * crossdomain file on both the port and the domain. 2. I also created a Securiy.allowDomain ("*").

Another thing. I also created another listener on the same server listening for connections for port 843 (the default) and this service just waited for the connection send policy file to be sent to the client and that's it.

That didn't solve the problem either ...

What's next? What should I do to fix this problem?

Appreciate your help.

Avi

+2


a source to share


3 answers


The fix for this issue is a dedicated policy file support server. I have implemented a socket listening on a dedicated port where flex looks for a policy file as soon as I received a connection and the request I responded to with the appropriate policy file.

This solved the problem for all users and works great for me.



thanks

+1


a source


Have you tried it Security.loadPolicyFile

? Has your server on the port ever actually received policy file requests (what the tiny XML sent to request a crossdomain policy file)? Does your actual server ever receive policy file requests? How much traffic are you getting on your server?



Greetz
back2dos

0


a source 


    .NET
    Add crossdomain.xml to your Web server root directory, for example, 
C:\inetpub\wwwroot.

    Java
    Add crossdomain.xml to \ArcGIS\java\web_output, for example, 
C:\Program Files\ArcGIS\java\web_output.

http://resources.esri.com/help/9.3/arcgisserver/apis/flex/help/content/deploy_application.htm

0


a source






More articles:


All Articles