archive-gh-me/node-http-proxy
1
0
Fork 0
mirror of https://github.com/http-party/node-http-proxy.git synced 2025-12-08 20:59:18 +00:00
Code Issues Projects Releases Wiki Activity

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.

Browse Source
This commit is contained in:
Drew Perttula 2012-02-06 17:15:44 -08:00
parent 868f7e7a28
commit 73e415a226
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -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: