This is all interesting. My reason for using node-http-proxy is that I have a fully featured programming language for rules in my proxy. It lets me rewrite in a very natural way, and inspect requests very deeply before determining which app to forward to.
If you are digging nginx, then keep at it. That's what I used to use when I was primarily deploying Rack apps with Unicorn, so I can admit that I love it (in fact, I make very heavy use of it on a wordpress site, and it works perfectly) On Sat, Apr 14, 2012 at 5:25 PM, mscdex <[email protected]> wrote: > On Apr 14, 2:25 pm, Dave <[email protected]> wrote: > > Perhaps I am missing something but I have not had any issues using > > nginx 1.1.18 proxying for a node server using Socket.IO. > > It depends on the browser too. I don't know if nginx 1.1.18 > specifically added support for older WebSocket specs (draft 75 or 76), > but the newer WebSocket specs no longer include a body in the HTTP > Upgrade request, so these WebSocket requests should travel safely > through proxies/reverse-proxies now. > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- chrisrhoden -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
