i have an app that opens a TCP socket to various user specified servers. prior to 3.0 this worked for all build targets including the webplayer. with 3.0 the webplayer will not open a connection. this happens in the editor and when run from the web host.
i’ve placed the below crossdomain.xml at the web root (and pretty much everywhere else). what must i do to get this working again?
<?xml version="1.0" ?>
<cross-domain-policy>
<allow-access-from domain="*" to-ports="*"/>
</cross-domain-policy>
that doesn’t really help. my app essentially telnets into various user specified servers. how am i expected to know what port, if any, an unknown server is supplying the XML on?
i obviously cannot control other servers. is this new “feature” of the web player saying that i simply cannot connect to servers that do not supply a crossdomain.xml file?
exactly
montgomery,
I know that type of security is annoying. It is something that we’ve been burdened with in the Flash world for years (pretty much an identical security policy). All servers that you want to connect to will have to serve the file. They’ll need to serve them up over the default port (943 I believe) or over whatever port you and the admins of those servers agree on. If it is a custom port then you’ll need to use the prefect method shown in the link above.
Good luck with your app. Security policies can be frustrating to say the least.