Curious if you've ever found an answer to this as we're finding something similar....?
Unfortunately,no. For the time being we are using the peek() option mentioned in the original post where we've 'special cased' our webserver.
We are disappointed in the lack of response from Adobe. So much so that we're looking into flex alternatives in our next release.
We're having a similar issue - we have the socket policy serving at 843 -- however we can't guarantee 843 will be open. We're connecting to 443 using the stomp protocol - I'm even telling the backend people here that flash will send a request on 443 and could we respond there - they say it can't be done.
And obviously the port 80 or security loadpolicyfile doesn't allow the socket connections without the 843 policy service.. .so we're stuck trying to find a way around this...and those in charge don't believe my answers as gospel.
Have you looked at this? Wondering if a socket policy can be served via some other 'standard' port -- telnet?
Access to socket and XML socket connections is disabled by default, even if the socket you are connecting to is in the same domain as the SWF file. You can permit socket-level access by serving a socket policy file from any of the following locations:
Port 843 (the location of the master policy file)
The same port as the main socket connection
A different port than the main socket connection
Sorry - last response.
The only other thing I can see is having two servers:
server1.url.com serves the actual files.
server2.url.com is the sockets. Don't have a webserver running on server2, use the common ports for socket communications and serving the policy file.
Has anoybody found a solution on the matter?