Custom Flash Services Port about socket.io HOT 4 CLOSED

As far as I know Flash sockets work as following.

First Flash will try port 843 and try get the policy file from there.
If however 843 doesn't respond with the policy Flash will try the port it was originally told to connect to.

So setting it to a custom port is kind of pointless. The policyfile should however be served over the destination port as well so that 843 can be turned off. (be warned tough if you dont use 843 all your clients will connect slower as first port 843 will be tried)

See http://www.adobe.com/devnet/flashplayer/articles/flash_player9_security_update.html especially "The policy file can be served from either the socket master policy port 843 or from the destination port of the socket connection".

from socket.io.

Thank you for the information. I was aware of the fallback, but an option would still be nice. (unless I NAT 843 to 8080 to get around the port hop, but that's kind of silly).

from socket.io.

Also, the reason a privileged port is needed is a valid one: you're determining the security restrictions for the entire domain(s) pointed to that computer. That's something only a superuser could do.

from socket.io.

Makes sense.

Perhaps have an option to turn it off so we can provide our own though other means on 843.
I just don't want to run my app as root. :\

from socket.io.