|
1782
|
1 #summary Adds support for flash socket policy |
|
|
2 #labels Stage-Alpha |
|
|
3 |
|
|
4 = Introduction = |
|
|
5 |
|
|
6 This Prosody plugin adds support for flash socket policies. When connecting with a flash client (from a webpage, not an exe) to prosody the flash client requests for an xml "file" on port 584 or the connecting port (5222 in the case of default xmpp). Responding on port 584 is tricky because it requires root priviliges to set up a socket on a port < 1024. |
|
|
7 |
|
|
8 This plugins filters the incomming data from the flash client. So when the client connects with prosody it immediately sends a xml request string ({{{<policy-file-request/>\0}}}). Prosody responds with a flash cross-domain-policy. See http://www.adobe.com/devnet/flashplayer/articles/socket_policy_files.html for more information. |
|
|
9 |
|
|
10 = Usage = |
|
|
11 |
|
|
12 Add "flash_policy" to your modules_enabled list. |
|
|
13 |
|
|
14 = Configuration = |
|
|
15 |
|
|
16 || crossdomain_file || Optional. The path to a file containing an cross-domain-policy in xml format. || |
|
|
17 || crossdomain_string || Optional. A cross-domain-policy as string. Should include the xml declaration. || |
|
|
18 |
|
|
19 Both configuration options are optional. If both are not specified a cross-domain-policy with "{{{<allow-access-from domain="*" />}}}" is used as default. |
|
|
20 |
|
|
21 = Compatibility = |
|
|
22 ||0.7||Works|| |
|
|
23 |
|
|
24 = Caveats/Todos/Bugs = |
|
|
25 |
|
|
26 * The assumption is made that the first packet received will always |
|
|
27 contain the policy request data, and all of it. This isn't robust |
|
|
28 against fragmentation, but on the other hand I highly doubt you'll be |
|
|
29 seeing that with such a small packet. |
|
|
30 * Only tested by me on a single server :) |
