Postman POST请求：Raw JSON正常，Form-data请求报错问题

Hey there! Let’s break down why your Form-data POST request is failing while Raw JSON works—this is a super common gotcha with Express/Node.js setups, so I’ve got a few targeted fixes and checks for you.

First, let’s start with the most likely culprit: missing middleware to parse Form-data requests. When you send Raw JSON, Express uses express.json() to parse the request body automatically, but Form-data (multipart/form-data) requires a different parser since it’s structured differently.

1. Add the right middleware for Form-data handling #

Express doesn’t parse multipart/form-data out of the box—you’ll need to use multer, the standard library for this job. Here’s how to set it up:

• First, install multer:

  npm install multer
  

• Then update your product.js route file to use it:

  const multer = require('multer');
  const upload = multer(); // Uses in-memory storage (perfect for text-only fields)
  
  // Apply the middleware to your POST route
  router.post('/', upload.none(), async (req, res) => {
    // Now req.body will contain your Form-data fields
    try {
      const newProduct = new Product(req.body);
      await newProduct.save();
      res.status(201).json(newProduct);
    } catch (err) {
      res.status(400).json({ message: err.message });
    }
  });
  

  Note: upload.none() tells multer to ignore file uploads and only parse text fields. If you need to handle files later, you can configure storage options, but this is the quick fix for your current issue.

2. Double-check field name matches #

When using Form-data, the key names in Postman must exactly match the fields defined in your product.model.js schema. Even a tiny typo (like productName vs productname) will cause validation errors because the data won’t map to your model correctly.

For example, if your schema looks like this:

const productSchema = new mongoose.Schema({
  name: { type: String, required: true },
  price: { type: Number, required: true }
});

In Postman’s Form-data tab, your keys need to be name and price—not Name or ProductName.

3. Log error details to pinpoint issues #

If you’re getting a vague error response, modify your route’s error handling to show exactly what’s failing. This will help you tell if it’s a missing field, data type mismatch, or parsing issue:

catch (err) {
  console.log('Full error:', err); // Check your terminal for details
  res.status(400).json({ 
    message: err.message,
    validationErrors: err.errors // Mongoose will show which fields failed validation
  });
}

4. Ensure express.json() isn’t conflicting #

Make sure your app’s middleware setup is correctly separated for JSON and Form-data:

const express = require('express');
const app = express();

// Parse Raw JSON requests (keep this)
app.use(express.json());

// Don't use express.urlencoded() for Form-data—this is for x-www-form-urlencoded only
// app.use(express.urlencoded({ extended: true })); 

Quick Test #

After setting up multer, send your Form-data request again. If req.body is now populated with your fields, the missing middleware was the problem. If not, double-check your field names and schema validation rules.

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