Skip to content

Commit 73e415a

Browse files
committed
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.
1 parent 868f7e7 commit 73e415a

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

README.md

+6
Original file line numberDiff line numberDiff line change
@@ -363,6 +363,12 @@ By default, `node-http-proxy` will set a 100 socket limit for all `host:port` pr
363363
1. By passing the `maxSockets` option to `httpProxy.createServer()`
364364
2. By calling `httpProxy.setMaxSockets(n)`, where `n` is the number of sockets you with to use.
365365

366+
## POST requests and buffering
367+
368+
express.bodyParser will interfere with proxying of POST requests (and other methods that have a request
369+
body). They'll never sending anything to the upstream server, and the original client will just hang.
370+
See https://github.com./nodejitsu/node-http-proxy/issues/180 for options.
371+
366372
## Using node-http-proxy from the command line
367373
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:
368374

0 commit comments

Comments
 (0)