Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improved english #205

Merged
merged 1 commit into from
Mar 2, 2012
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -366,8 +366,8 @@ By default, `node-http-proxy` will set a 100 socket limit for all `host:port` pr
## 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.
body). With bodyParser active, proxied requests will never send 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:
Expand Down