On 16/12/2012 07:58, Nick Zavaritsky wrote:
According to the roadmap at http://trac.nginx.org/nginx/roadmap, the support for
websockets is planned for release in 2 month. Is there any preview code available
yet? It would be nice to start playing with this feature early on.
Since this is going to be used in my pet project the possible instability
doesn’t scare me much.
Further information from my testing. It appears that using
nginx-tcp-proxy-module can only handle websockets on a different port to
This is no use to me. Many of our potential users are commercial and
lock down outgoing ports to 80 and 443 only.
Does anyone connected with the development of the new software know if
it will enable nginx to separate websocket and other traffic by domain
I expected to use a sub-domain rather than location for connections that
are to be upgraded to websockets. That will start things off properly -
after that the link is the link, so the sub-domain is not relevant. (Or
is my understanding of networking faulty?)