简体   繁体   中英

Node (express.js) next() is called before end of stream

I have the following middleware function

var bodyParser = require('body-parser'),
  fs = require('fs');
module.exports = function(req, res, next) {
  // Add paths to this array to allow binary uploads
  var pathsAllowingBinaryBody = [
    '/api2/information/upload',
    '/api2/kpi/upload',
  ];

  if (pathsAllowingBinaryBody.indexOf(req._parsedUrl.pathname) !== -1) {
    var date = new Date();
    req.filePath = "uploads/" + date.getTime() + "_" + date.getMilliseconds() + "_" + Math.floor(Math.random() * 1000000000) + "_" + parseInt(req.headers['content-length']);

    var writeStream = fs.createWriteStream(req.filePath);
    req.on('data', function(chunk) {
      writeStream.write(chunk);
    });
    req.on('end', function() {
      writeStream.end();
      next();
    });
  } else {
    bodyParser.json()(req, res, next);
  }
};

The files is being transfered correctly however sadly the next() in the

req.on('end', function() {
  writeStream.end();
  next();
});

is called before it is done writing all data to the new file.

My question is what am i doing wrong? And how can i fix it?

Use the writable file stream's close event to know when the file descriptor has been closed.

Replace this:

var writeStream = fs.createWriteStream(req.filePath);
req.on('data', function(chunk) {
    writeStream.write(chunk);
});
req.on('end', function() {
    writeStream.end();
    next();
});

with this:

req.pipe(fs.createWriteStream(req.filePath)).on('close', next);

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM