StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Crossdomain policy file should be hosted on machine where the server is running i.e. on the 23.29.126.76. For socket connection flash players automatically try to load master crossdomain policy file from the port 843 (You can get simple policy server script from adobe.com <a href="http://www.adobe.com/cn/devnet/flashplayer/articles/socket_policy_files.html" rel="nofollow">http://www.adobe.com/cn/devnet/flashplayer/articles/socket_policy_files.html</a>)</p> <p>UPD: Use <code>Security.loadPolicyFile("xmlsocket://23.29.126.76:843");</code> to load policy file directly, but as I wrote flash player already do the same automatically (for port 843), it sends the string request <code>"<policy-file-request/>\0"</code>. </p> <p><strong>debugging policy</strong></p> <p>To debug the policy server do the following:</p> <ol> <li><p>Be sure you have the <a href="http://www.adobe.com/support/flashplayer/downloads.html" rel="nofollow">debug flash player</a>.</p></li> <li><p>Check that server installing is correct by the command (linux, mac or cygwin on Windows): <code>echo -ne '<policy-file-request/>\0' | nc -v host port</code>. This command should print out your crossdomain.xml file</p></li> <li><p>Turn on the flash player policy log by setting the flag <code>PolicyFileLog=1</code> in <a href="http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fc9.html" rel="nofollow">mm.cfg</a> file (be sure you have the <a href="http://www.adobe.com/support/flashplayer/downloads.html" rel="nofollow">debug version</a> of flash player), run swf file and read the policy log, it has user friendly format, you will be able to figure out the problem in most cases by this log.</p></li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload