Afficher un message
Vieux 07/04/2008, 23h11   #1
jkc7297
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Flash new security socket policy issue.

Hi all

We heard that Adobe is going to change the socket security and forcing the
corssdomain file to be serve through a socket server. So we implement a socket
server that will feed the crosssdomain.xml when flash ask for the policy file
at port 8080 (Notice not the 843). Everything is good until we notice there is
warning in the flash debug log.

=============
OK: Searching for <allow-access-from> in policy files to authorize data
loading from resource at xmlsocket://<remove>:8080 by requestor from
http://<remove>.swf

Warning: Timeout on xmlsocket://<remove>:843 (at 3 seconds) while waiting for
socket policy file. This should not cause any problems, but see
http://www.adobe.com/go/strict_policy_files for an explanation.

OK: Policy file accepted: xmlsocket://<remove>:8080

OK: Request for resource at xmlsocket://<remove>:8080 by requestor from
http://<remove>.swf is permitted due to policy file at xmlsocket://<remove>:8080
=============

We figure since there is the loadpolicyfile function call, we can tell flash
to load the policyfile from the port 8080 and forget about the port 843.

Security.loadPolicyFile("xmlsocket://" + host + ":8080")

We get the same result even we have the Security.loadpolicyfile call telling
it to use 8080 port.

We would like to NOT use the port 843.
We also would like to avoid the 3 second delay cause by the flash lookup at
the port 843.


My question is.
Is there anyway to tell Flash to just look at port 8080 and forget about port
843 for the policyfile?


Thanks in advance

  Réponse avec citation
 
Page generated in 0,06234 seconds with 9 queries