Add important note about 'body-parser'

[sebastienroul]

I spent 2 days to find my issue. It was very hard to find the problem, but in some case, the body-parser change the body POST, and thn this body post is not sent to the target correctly. Hope it helps

[ShragaUser]

@sebastienroul hey! just to clarify - what exactly was the issue with the post body?

[sebastienroul]

@ShragaUser The post body was a form-urlencoded from a basic html form. The think I notice was when we had, in the html form the same input present 2 times then the body was {foo: ['X', 'X']} after the body parser.
With the body-parser before, the proxy request was not recognizided by the proxied server, and when we put it after, the request was accepted.
At the begining we spend lot of time to search pb in the http-proxy, but in fact it was somewhere else ;)

Take a look at chimurai/http-proxy-middleware#299 it's this one who put me on the track !
So, just an info in the doc would save time :o)

Bye

[aztack]

Same here! the proxy MUST be put before app.use(bodyParser.json()) otherwise, POST requests are forwarded without the body. But you can not find out in the Chrome network panel. Chrome shows that everything is correct. After sniffing the requests with Wireshark, I found that the POST request body is not even there.

[monkpow]

Thanks!