node-http-proxy

I have a simple Express based Node.js web server that I'm using for development of a JavaScript application. I set up the server to use node-http-proxy to proxy API requests the application makes to a Jetty server that is running on a different domain and port. This setup has been working flawlessly until I started to run into problems with session management. Upon authentication the application server returns a cookie with an auth token representing the server session. When I run the JS application off of my filesystem (file://) I can see that once client receives the cookie, it is sent in

I have an application that uses websockets via socket.io. For my application I would like to use a separate HTTP server for serving the static content and JavaScript for my application. Therefore, I need to put a proxy in place. I am using node-http-proxy . As a starting point I have my websockets app running on port 8081. I am using the following code to re-direct socket.io communications to this standalone server, while using express to serve the static content: var http = require('http'), httpProxy = require('http-proxy'), express = require('express'); // create a server var app = express()

Here's the module version that I'm using: $ npm list -g | grep proxy ├─┬ http-proxy@0.10.0 A webservice calls into my machine and my task is to proxy the request to a different url and host with an additional query parameter based on the contents of the request's body: var http = require('http'), httpProxy = require('http-proxy') form2json = require('form2json'); httpProxy.createServer(function (req, res, proxy) { // my custom logic var fullBody = ''; req.on('data', function(chunk) { // append the current chunk of data to the fullBody variable fullBody += chunk.toString(); }); req.on('end',

I'm trying to get websockets to also work with node-http-proxy . The difference is i'm using a proxytable: var options = { router: { 'a.websterten.com': '127.0.0.1:150', 'b.websterten.com' : '127.0.0.1:151', } }; var server = httpProxy.createServer(options); I tried: server.on('upgrade', function (req, socket, head) { server.proxy.proxyWebSocketRequest(req, socket, head); }); But it doesn't seem to work. A quick check to see whether websockets work shows I get Unexpected response code: 400 from Chrome (works fine if I go directly) Also doing a couple of checks server.on('upgrade',.. doesn't

Tell me please what is preferable to use for deployment of nodejs applications nginx or node-http-proxy. What is most robust? The basic features I need are proxy all requests to non 80 post load balancer Websocket supporting Here is a great article on the subject http://www.exratione.com/2012/07/proxying-websocket-traffic-for-nodejs-the-present-state-of-play/ Personally I have played with a lot of configurations in this realm and it all comes down to what you need and where you need to deploy. If you are on your own hardware (or cloud slice, etc.) and you only need to support Node, then node

I'm trying to do something like this: // Setup prox to handle blog requests httpProxy.createServer({ hostnameOnly: true, router: { 'http://localhost': '8080', 'http://localhost/blog': '2368' } }).listen(8000); Previously I was using this: http.createServer(app).listen(app.get('port'), function(){ console.log("Express server listening on port " + app.get('port')); }); Basically, I want to still use express... but, when people go to http://localhost/blog get taken to the blog but still be served over port 8080 (which will eventually be port 80) So I switched it to this and it worked better. The