# Websockets **URL:** \ **Category:** NGINX\ **Created:** [December 16, 2012, 8:59am UTC](https://www.ruby-forum.com/t/websockets/226559 "2012-12-16T08:59:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Nick\_Zavaritsky](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/b9e5f3/32.png) [@Nick\_Zavaritsky](https://www.ruby-forum.com/u/Nick_Zavaritsky)\ **Post date:** [December 16, 2012, 8:59am UTC](https://www.ruby-forum.com/t/websockets/226559/1 "2012-12-16T08:59:15Z")
Hi! According to the roadmap at [Roadmap – nginx](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. ---
**Author:** ![Nick\_Zavaritsky](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/b9e5f3/32.png) [@Nick\_Zavaritsky](https://www.ruby-forum.com/u/Nick_Zavaritsky)\ **Post date:** [December 17, 2012, 9:29am UTC](https://www.ruby-forum.com/t/websockets/226559/2 "2012-12-17T09:29:41Z")
Hi Nick, On 12/16/12 11:58 AM, Nick Zavaritsky wrote: > Hi! > > According to the roadmap at [http://trac.nginx.org/nginx/roadmap](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. The roadmap is correct but no such code available yet. Ping us again in mid-January. – Maxim K. +7 (910) 4293178 > **[F5 NGINX: Built for cloud-native apps. Ready for AI traffic.](https://www.f5.com/products/nginx)** > > Deliver modern applications with NGINX. Explore high-performance load balancing, API gateways, and web server solutions trusted by top global enterprises. ---
**Author:** ![Nick\_Zavaritsky](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/b9e5f3/32.png) [@Nick\_Zavaritsky](https://www.ruby-forum.com/u/Nick_Zavaritsky)\ **Post date:** [December 18, 2012, 7:47pm UTC](https://www.ruby-forum.com/t/websockets/226559/3 "2012-12-18T19:47:12Z")
On 17/12/2012 08:29, Maxim K. wrote: > The roadmap is correct but no such code available yet. Ping us > again in mid-January. I want to use websockets also, and found [http://yaoweibin.github.com/nginx\_tcp\_proxy\_module/](http://yaoweibin.github.com/nginx_tcp_proxy_module/) which may provide web-sockets now. I have only got as far as compiling it into 1.2.6 - so no testing done yet. Regards Ian – Ian H. 31 Sheerwater, Northampton NN3 5HU, Tel: 01604 513875 Preparing eBooks for Kindle and ePub formats to give the best reader experience. ---
**Author:** ![Nick\_Zavaritsky](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/b9e5f3/32.png) [@Nick\_Zavaritsky](https://www.ruby-forum.com/u/Nick_Zavaritsky)\ **Post date:** [December 19, 2012, 9:03pm UTC](https://www.ruby-forum.com/t/websockets/226559/4 "2012-12-19T21:03:12Z")
On 16/12/2012 07:58, Nick Zavaritsky wrote: > Hi! > > According to the roadmap at [http://trac.nginx.org/nginx/roadmap](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 http traffic. ☹ 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 name. 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?) thanks Ian ---
**Author:** ![Nick\_Zavaritsky](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/b9e5f3/32.png) [@Nick\_Zavaritsky](https://www.ruby-forum.com/u/Nick_Zavaritsky)\ **Post date:** [December 18, 2012, 8:22pm UTC](https://www.ruby-forum.com/t/websockets/226559/5 "2012-12-18T20:22:15Z")
+1 for websocket waiting list… ---
**Author:** ![Nick\_Zavaritsky](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/b9e5f3/32.png) [@Nick\_Zavaritsky](https://www.ruby-forum.com/u/Nick_Zavaritsky)\ **Post date:** [December 20, 2012, 4:36am UTC](https://www.ruby-forum.com/t/websockets/226559/6 "2012-12-20T04:36:01Z")
On Dec 20, 2012, at 0:02, Ian H. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 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 name. Our implementation will be fully compatible with the existing proxy\_pass semantics, including upstream server groups, load balancing etc. > I expected to use a sub-domain rather than location for connections that are to > be upgraded to websockets. That should be ok. Btw, we still have one sponsorship seat vacant. Email to nginx-inquiries at nginx dot com if this something that might be interesting for you guys.