-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/policy #273
Feature/policy #273
Conversation
…forward 843 on the server side
…t is answered using the net server on a different port
My personal preference for a default non root port goes to |
:) Ah, great. Hope this lands soon. |
@dshaw same, just got to make one more small adjustment, we want to use a non root port by default. We just have to come up with a port number for it :) |
:2030 works. I actually use this to force the request on :80 to deal with fire wall request swallowing. |
Isn't this about websockets? How is it related to flash sockets and root being required? :) |
@tommedema this isn't about websockets, the flashsocket requires a net.Server that can respond the flashplayer's origin authentication / crossdomain.xml requests. Currently they default to port 843, but with this fix that is no longer needed |
@3rd-Eden, ah. That's excellent. Great find. |
I discovered this nice hidden undocumented gem in the
web-socket-js
project when I was skimming through the source.. By default it will retrieve it from the by default suggest port number843
but this port requires root privileges. So normally people would set up IP tables or proxies to do port forwarding of 843 to a non root port.This just makes all that stuff so much easier, you can just define a different port on the server and client and you are done with it ^_^ <3
Tested it, and it works like charm.. We might want to set a non root port by default both on the server and on the client..
Opinions on that are more than welcome.