node-http-proxy

There's several ways to have a blog path contain a separate setup from the marketing/product routes. One is to run a reverse proxy on the root domain to pull in separate routes for various services. https://github.com/http-party/node-http-proxy You can do rewrites at the server level for the root domain Or if the app on the root domain can do the routing for you (have done this before with a Rails app)

I've been building a list of apps and libraries in this space. In no particular order: https://requestly.io/ https://portswigger.net/burp https://dutzi.github.io/tamper/ https://anyproxy.io/en/ https://wproxy.org/whistle/ https://www.telerik.com/fiddler https://github.com/alibaba/lightproxy https://httptoolkit.tech/ https://mitmproxy.org/ https://wiki.squid-cache.org/Features/SslPeekAndSplice https://www.charlesproxy.com/ https://nssurge.com/ https://wrapapi.com/proxy https://www.privoxy.org/ http://www.tofuproxy.stargrave.org/ https://github.com/http-party/node-http-proxy https://github.com/joeferner/node-http-mitm-proxy https://www.zaproxy.org/ https://proxyman.io

Start with an open source http proxy http://www.catonmat.net/http-proxy-in-nodejs/ https://github.com/nodejitsu/node-http-proxy

You're on to me. ;) There is node-http-proxy available (https://github.com/nodejitsu/node-http-proxy), which also has some plugins available to do some of the advanced features nginx supports. I'll likely be writing a custom proxy server tailored to our needs such that it probably won't be useful as a general purpose proxy server, but if you're looking for something, that's a start. Making it more general purpose unfortunately would require more work, and I'm pretty time stretched right now. I'm not saying it's better than nginx, of course. I'm just saying that if you need to do some crazy programming that can't be done with nginx, you're free to use something else. Don't be fearful of treading your own path, just make sure you know well how HTTP works before doing it. Here's a stupid example I whipped up quickly for a reverse proxy for o

I've had good results so far with node-http-proxy: https://github.com/nodejitsu/node-http-proxy/ Easy to set up, and has the benefit of reducing the number of processes I need to maintain (my node server and my proxy server are the same).

We're using this to reverse proxy websockets over SSL and it's simple and wonderfully stable. https://github.com/nodejitsu/node-http-proxy

Hipache is built on top of node-http-proxy [1], a nodejs library which implements a lot of the actual websocket logic. Most of the tests you have in mind are in that library. Hipache implements a management and automation layer on top of it, and although more tests are always good, in my experience full-stack integration tests are more important in that context. I am not the author, but I work at dotCloud and can tell you that Hipache was submitted to massive amounts of integration testing and load testing before even touching its first production deployment. Obviously there's a long way to go before being as battle-tested as squid or nginx, but we're not talking about a week-end hack project either. [1] http://github.com/nodejitsu/node-http-proxy

Node Http Proxy: https://github.com/nodejitsu/node-http-proxy No need for Varnish for proxying your websockets.

I'm experimenting with the nodejitsu node-http-proxy (https://github.com/nodejitsu/node-http-proxy), and my super simple proxy seems to be working well. I've just tried surfing around to a bunch of sites I normally visit, and they've loaded fine. Unfortunately, when I try to load HN with the proxy running, I just get a blank screen that says "Unknown." Does anyone know anything about that? Experienced it before?

> It looks like it is claiming to support lots of internode cluster-type communication There are a few projects that specifically take advantage of node's ability to proxy and distribute work across multiple processes. Check out these projects: http://learnboost.github.com/cluster/ https://github.com/nodejitsu/node-http-proxy https://github.com/substack/dnode Or my very early prototype botnet thingie: https://github.com/isaacs/sodn

https://github.com/nodejitsu/node-http-proxy/commits/v0.3.1 You're a partisan in this matter, I don't think I can take you seriously.

Looking really good indutny! For anyone interested, Fedor is also one of the co-authors of node-http-proxy ( https://github.com/nodejitsu/node-http-proxy ) and an all around nice guy.

NodeFu is not a company but rather an open source project. It does use the http-proxy module - https://github.com/nodejitsu/node-http-proxy

Logo and company name seems very similar to http://www.nodejitsu.com It's also curious NodeFu seem to be using some of Nodejitsu's open-source offerings to make this work. ( https://github.com/nodejitsu/node-http-proxy and https://github.com/indexzero/forever ). Are NodeFu and Nodejitsu the same company?