Replies: 9 comments
-
mount your |
Beta Was this translation helpful? Give feedback.
-
Thanks for the suggestion. I did try this. I get a working proxy, but get 'undefined' for req.body (probably because then bodyParsers are now after my app.use() that dumps the data.) If I put apiProxy before my app.use(), my app.use() never gets called. |
Beta Was this translation helpful? Give feedback.
-
Update - I had success using the npm 'body' package rather 'body-parser'. |
Beta Was this translation helpful? Give feedback.
-
@garyns work for me |
Beta Was this translation helpful? Give feedback.
-
@garyns can you tell the sample how it worked for you. When I am using npm body still my socket is hanging. |
Beta Was this translation helpful? Give feedback.
-
can you please show an example of how to use body ? |
Beta Was this translation helpful? Give feedback.
-
Hi @chimurai Would you mind adding the "mount your apiProxy before mounting the bodyParser middlewares" nugget to the README file? I just spent three days trying to figure out why my proxy was hanging, until I stumbled upon this issue. Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Found that it is possible to do it with the bodyParser middleware by following this example which shows the need to re-stream the body in the |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm trying to create a small development proxy to print out to the console headers, query params, and body.
But I can't get the body and prioxy to work together, and all my research had not given me any obvious solution.
In the code below, when I enable bodyParsers, I get the body printed to the console, but any PUT or POST request that contains a body ends up hanging. With no bodyParsers, req.body is undefined (as pre express docs) and the proxied request completes successfully.
Any advise on how I might approach this?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions