I'm attempting to pipe a request for handling by a remote server, along the following lines:
var destination = request(url);
req.pipe(destination).pipe(res);
This works just fine for GET
requests. But for POST
requests I'm struggling. An important point to note, I think, is that for POST
requests I'm using a body parser before my POST
route handler in order to extract the body from the POST
request... it's just a basic text body parser because the body contains plain text:
var postRouteHandler = someFunction;
var bodyParser = require('body-parser');
var textParser = bodyParser.text({
limit: '50kb'
});
app.use('/postRoute', [textParser, postRouteHandler]);
From this issue and this issue it seems to me that doing any processing on the POST
request before you pipe it will cause a problem. Indeed, when I remove the parser, the piping seems to work OK.
The problem is that I need to examine the body first, to do some initial processing and then to determine whether or not to pipe the request on to the remote server at all. So I need to parse the body before piping.
Is there any way around this problem?
Text body parser To use the Text body parser, we have to write app. use(bodyParser. text()) and the Content-Type in your fetch API would be text/html . That's it, now your backend service will accept POST request with text in the request body.
In order to get access to the post data we have to use body-parser . Basically what the body-parser is which allows express to read the body and then parse that into a Json object that we can understand. Save this answer.
Express has a built-in express. json() function that returns an Express middleware function that parses JSON HTTP request bodies into JavaScript objects. The json() middleware adds a body property to the Express request req . To access the parsed request body, use req.
'bodyParser' is deprecated. // If you are using Express 4.16+ you don't have to import body-parser anymore.
The issue is that with streams (like req
), once you've read it you can't reset it.
Because body-parser
has read the stream already, piping it won't work because that will try to read the stream again (which at that point has been exhausted).
A workaround would be take the text read by body-parser
, and create a minimal req
"clone" in order for request
to be able to pass the request along:
var intoStream = require('into-stream');
var bodyParser = require('body-parser');
var textParser = bodyParser.text({ limit: '50kb' });
var postRouteHandler = function(req, res) {
let text = req.body;
if (! shouldPipe(text)) {
return res.sendStatus(400); // or whatever
}
// Here's where the magic happens: create a new stream from `text`,
// and copy the properties from `req` that `request` needs to pass
// along the request to the destination.
let stream = intoStream(text);
stream.method = req.method;
stream.headers = req.headers;
// Pipe the newly created stream to request.
stream.pipe(request(url)).pipe(res);
};
app.use('/postRoute', [textParser, postRouteHandler]);
You should create your own middleware if the parser is causing the problem. In all honesty you may want to parse the body a different way than the body parser.
Given the limited knowledge about what the rest of your project is doing you could create middleware to hook the body parser middleware and just send a clone of request. This however is not very efficient but will work and may help point you in the right direction.
var postRouteHandler = someFunction;
var bodyParser = require('body-parser');
var textParseMiddleware = function (req, res, next) {
var requestclone = _.clone(req);
var textParser = bodyParser.text({
limit: '50kb'
});
textParser(requestclone, res, function(){
console.log('examine the body here', requestclone.body);
});
}
app.use('/postRoute', [textParserMiddleWare, postRouteHandler]);
I have not tested the above code.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With