Feature #357
Crossdomain.xml sent through xmlsocket:3000 on connection
| Status: | New | Start: | 06/10/2009 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | Version 1.3 (Community Core Release) | Estimated time: | 2.00 hours | |
Description
Hi,
Since new security features in flashplayers 9 and 10 oblige flash external swf's to obtain a second crossdomain.xml directly through the connecting socket(port 3000). Would it be possible to add support for this by either sending a generic crossdomain.xml file at all first flash client connections.
Or to build support for it in the app ?
Best regards,
Karel.
History
Updated by Dean North over 3 years ago
Anonymous wrote:
Hi,
Since new security features in flashplayers 9 and 10 oblige flash external swf's to obtain a second crossdomain.xml directly through the connecting socket(port 3000). Would it be possible to add support for this by either sending a generic crossdomain.xml file at all first flash client connections. Or to build support for it in the app ?
Best regards, Karel.
This show not be done through port 3000, it should be through the master policy socket (port 843) and the crossdomain.xml it sends should allow the common TUIO ports (3333 and 3000).
More information on the master policy socket can be found here...
http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security_05.html#_Configuring_Socket_Policy
This is what I used to make TouchGateway and it works like a charm.
Regards
Pleh
