it's unlikely (but possible) that anyone will download and correct your files. especially because, from your title, the problem is not likely to be found in your files.
you probably need cross-domain policy files.
I run Server with Appserv.
I created the crossdomain.xml file at Localhost.
<? Xml version = "1.0"?>.
<! DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">.
<allow-access-from domain="*" />.
But still the message. <policy-file-request/>. Same.
to where is your xmlsocket trying to connect?
I have been tested by No-IP.
Xmlsocket then connected to "newaxekub.no-ip.info" and I have Forward port 8000
Xmlsocket connect to my WAN IP.
When someone Login.
javaserver will display a message "192.168.1.2 [newaxekub] connected.".
But I upload swf file to my hosting. When someone Login.
javaserver will display a message that 192.168.1.2 [<policy-file-request/>] connected.
you need a master policy file in the root of newaxekub.no-ip.info
Thank you very much. Now I have already connected.
Just now also believed to be.
But this can not be isolated.
Do not know is why.
give me some sample policy file please.
I am sorry to use the language incorrectly.
I used translate.google Thai to English.
Please help me.
<!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
this should be in the root and allows all policy files but gives access to no domains.
a policy file (eg, crossdomain2.xml) in a subdirectory with allow-access-from allows domain access to
the directory, and dependent subdirectories, that contain crossdomain2.xml
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
this policy file (eg, crossdomain2.xml) is in a directory it will allow access to that directory and its subdirectories
IF there's a root policy file (eg, crossdomain.xml) allowing cross-domain-policies
<allow-access-from domain="www.kglad.com" />
Thank you for all answer.
At first, it works, it shows a user when the user added.
But after that it displays a message. [<policy-file-request/>] The same.
Then it displays the message. [<policy-file-request/>] As a user added.
I followed the advice of Kglad.
I create a crossdomain.xml to the Root of Localhost.
And create crossdomain2.xml at Root of Localhost.
At first, there is no problem. But later it was the same.