Node.js+Firebase Functions中Busboy处理POST请求失败求助

问题重现 #

本地Node.js环境用Busboy处理multipart/form-data类型POST请求完全正常，但部署到Firebase Functions后，Postman返回Error: could not handle the request，具体报错：

Error: Unexpected end of form
    at Multipart._final (/workspace/node_modules/busboy/lib/types/multipart.js:588:17)
    at callFinal (node:internal/streams/writable:696:27)
    at prefinish (node:internal/streams/writable:725:7)
    at finishMaybe (node:internal/streams/writable:735:5)
    at Multipart.Writable.end (node:internal/streams/writable:633:5)
    at onend (node:internal/streams/readable:693:10)
    at processTicksAndRejections (node:internal/process/task_queues:78:11)

相关代码 #

index.js #

var busboy = require('connect-busboy');

app.use(busboy());

app.use(cors()); 

const portCheck = process.env.PORT || 3001

app.use(express.json({limit: "50mb"}));
app.use(express.urlencoded({limit: "50mb", extended: true}));

app.use(cookieParser());
// 静态文件路由注释略

userProfile.js #

router.post('/userprofile/check/busboy', async (req,res) => {
  console.log(req.body);
  
  const fields = {};
  req.busboy.on('field', (name, val) => {
    console.log('reached till here');
    
      console.log(`Processed field ${name}: ${val}.`);
    
    
    fields[name] = val;
    console.log(fields);
  });

  req.busboy.on('finish', function() {
    console.log('Done parsing form!');
    res.status(201).send();
  });
  
  req.pipe(req.busboy);
})

问题原因 #

Express的express.json()和express.urlencoded()中间件会提前消费请求体流，当Busboy尝试读取时，流已经被读完，导致出现"Unexpected end of form"错误。本地环境可能因为流的可重读特性不会触发，但Firebase Functions的请求流是不可重读的，因此问题在部署后暴露。

解决方案 #

1. 避免body解析中间件处理multipart请求 #

修改index.js，让Express仅对非multipart/form-data类型的请求应用body解析：

var busboy = require('connect-busboy');
const express = require('express');
const app = express();

// 先注册busboy中间件
app.use(busboy());

app.use(cors()); 
app.use(cookieParser());

// 仅对非multipart请求应用json解析
app.use((req, res, next) => {
  if (!req.is('multipart/form-data')) {
    express.json({limit: "50mb"})(req, res, next);
  } else {
    next();
  }
});

// 仅对非multipart请求应用urlencoded解析
app.use((req, res, next) => {
  if (!req.is('multipart/form-data')) {
    express.urlencoded({limit: "50mb", extended: true})(req, res, next);
  } else {
    next();
  }
});

const portCheck = process.env.PORT || 3001
// 其他代码不变

2. 改用原生Busboy替代connect-busboy #

connect-busboy是封装层，直接使用原生Busboy可减少中间件冲突，修改userProfile.js：

const Busboy = require('busboy'); // 注意这里是原生Busboy，不是connect-busboy

router.post('/userprofile/check/busboy', async (req,res) => {
  const busboy = new Busboy({ headers: req.headers });
  const fields = {};

  busboy.on('field', (name, val) => {
    console.log(`Processed field ${name}: ${val}.`);
    fields[name] = val;
    console.log(fields);
  });

  busboy.on('finish', () => {
    console.log('Done parsing form!');
    res.status(201).send();
  });

  // 添加错误处理，避免未捕获异常导致请求崩溃
  busboy.on('error', (err) => {
    console.error('Busboy解析错误:', err);
    res.status(500).send('表单处理失败');
  });

  req.pipe(busboy);
})

3. 检查Firebase Functions资源配置 #

如果请求体较大（比如包含文件），需要调整Firebase Functions的资源限制：

• 进入Firebase控制台 → 目标项目 → 云函数 → 找到对应函数 → 编辑 → 调整内存配额（建议至少512MB）和超时时间（最长9分钟）。

验证 #

部署修改后的代码到Firebase Functions，用Postman重新发送multipart/form-data请求，确认错误消失，请求正常处理。

内容的提问来源于stack exchange，提问作者akm