# Feature request: WebSocket proxying :-) **URL:** \ **Category:** NGINX\ **Created:** [September 12, 2010, 6:59am UTC](https://www.ruby-forum.com/t/feature-request-websocket-proxying/194845 "2010-09-12T06:59:05Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jwigal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/6a8cbe/32.png) [@jwigal](https://www.ruby-forum.com/u/jwigal)\ **Post date:** [September 12, 2010, 6:59am UTC](https://www.ruby-forum.com/t/feature-request-websocket-proxying/194845/1 "2010-09-12T06:59:05Z")
Hi all… but mostly Igor, 😉 I know many others have requested HTTP/1.1-to-upstream support for all kinds of reasons. This request is perhaps slightly more focused. I would _really_ like to put nginx in front of my WebSocket servers (for which I use node.js, but there are popular Python and Ruby implementations too). There are lots of good reasons to put nginx in front of a WebSocket server: you might want to serve static files (efficiently!) on the same port, only worry about SSL in nginx and not the backend, or running multiple WebSocket upstreams behind a load-balancing nginx frontend… Igor, is this something you’ve considered or looked at, or would you wait until it made sense to do an HTTP/1.1 (to upstream) implementation? Thanks, - Jeff – Ubuntu’s Bleeding Edge > **[Ubuntu’s Bleeding Edge](https://ubuntuedge.wordpress.com/)** > > Tracking Ubuntu’s development branch, so you don't have to! \* ``` "I don't even understand offside so I'm not likely to understand a Manchester United contract." - Posh Spice ``` ---
**Author:** ![jwigal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/6a8cbe/32.png) [@jwigal](https://www.ruby-forum.com/u/jwigal)\ **Post date:** [September 14, 2010, 10:54am UTC](https://www.ruby-forum.com/t/feature-request-websocket-proxying/194845/2 "2010-09-14T10:54:23Z")
Jeff W. at 2010-9-12 12:58 wrote: > you might want to serve static files (efficiently!) on the same port, only > worry about SSL in nginx and not the backend, or running multiple WebSocket > upstreams behind a load-balancing nginx frontend… > > Igor, is this something you’ve considered or looked at, or would you wait > until it made sense to do an HTTP/1.1 (to upstream) implementation? How about use my nginx\_tcp\_proxy\_module? ([GitHub - yaoweibin/nginx\_tcp\_proxy\_module: add the feature of tcp proxy with nginx, with health check and status monitor · GitHub](http://github.com/yaoweibin/nginx_tcp_proxy_module))。 > Thanks, > > - Jeff – Weibin Y. ---
**Author:** ![jwigal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/6a8cbe/32.png) [@jwigal](https://www.ruby-forum.com/u/jwigal)\ **Post date:** [November 26, 2011, 10:58pm UTC](https://www.ruby-forum.com/t/feature-request-websocket-proxying/194845/3 "2011-11-26T22:58:05Z")
Hello! On Sat, Nov 26, 2011 at 08:55:46AM -0500, WGH wrote: > Bump! HTTP/1.1 proxying is now being implemented in devel version of > nginx, for unfortunately important headers like “Upgrade” and > “Connection” are still stripped/replaced. It’s not enough to talk HTTP/1.1 to proxy WebSockets. It requires either talking WebSockets protocol or being able to establish opaque pipe between client and backend. Maxim D. ---
**Author:** ![jwigal](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/6a8cbe/32.png) [@jwigal](https://www.ruby-forum.com/u/jwigal)\ **Post date:** [November 26, 2011, 2:56pm UTC](https://www.ruby-forum.com/t/feature-request-websocket-proxying/194845/4 "2011-11-26T14:56:16Z")
Bump! HTTP/1.1 proxying is now being implemented in devel version of nginx, for unfortunately important headers like “Upgrade” and “Connection” are still stripped/replaced. > How about use my nginx\_tcp\_proxy\_module? > You can’t use the same listening port with HTTP modules. > No. Posted at Nginx Forum: [http://forum.nginx.org/read.php?2,129658,219111#msg-219111](http://forum.nginx.org/read.php?2,129658,219111#msg-219111)