From 73e415a22634bfc9e5993377902f67ac3212714a Mon Sep 17 00:00:00 2001 From: Drew Perttula Date: Mon, 6 Feb 2012 17:15:44 -0800 Subject: [PATCH] Address ticket #180 here since that problem is so hard to discover when you run into it. If there was an error, people would search for the error text, but there isn't. --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 77fc3f3..0b20ffc 100644 --- a/README.md +++ b/README.md @@ -363,6 +363,12 @@ By default, `node-http-proxy` will set a 100 socket limit for all `host:port` pr 1. By passing the `maxSockets` option to `httpProxy.createServer()` 2. By calling `httpProxy.setMaxSockets(n)`, where `n` is the number of sockets you with to use. +## POST requests and buffering + +express.bodyParser will interfere with proxying of POST requests (and other methods that have a request +body). They'll never sending anything to the upstream server, and the original client will just hang. +See https://github.com/nodejitsu/node-http-proxy/issues/180 for options. + ## Using node-http-proxy from the command line When you install this package with npm, a node-http-proxy binary will become available to you. Using this binary is easy with some simple options: