I believe there is a way of specifying where the policy file (by which I assume you mean crossdomain.xml) is located. I find it surprising that it is switching ports on you as well. But maybe that can only request the crossdomain.xml as an http request, and doesn't assume that the you have a http server listening on the same port as the xml socket? On Thu, Oct 23, 2008 at 12:43 PM, <[EMAIL PROTECTED]> wrote:
> > All, > I have a flex application that opens a socket to my web server. I set up > the socketpolicy script on port 843. However it seems that my > application never attempts to connect to port 843. Instead it tries to > request the policy file directly from the port I am trying to open. I > thought it would try 843 first. > Is there something I need to do in the code to tell it to try 843 first. > Thanks. > > > ------------------------------------------------------------- > To unsubscribe from this list, simply email the list with unsubscribe in > the subject line > > For more info, see http://www.affug.com > Archive @ http://www.mail-archive.com/discussion%40affug.com/ > List hosted by http://www.fusionlink.com > ------------------------------------------------------------- > > > -- Scott Talsma CTO, echoEleven ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
