Parsing request body (JSON and form data) in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of parsing the request body in a Node.js server?

Parsing the request body allows the server to read and understand data sent by the client, such as form inputs or JSON payloads, so it can respond appropriately.

beginner

Which Node.js middleware is commonly used to parse JSON request bodies?

The built-in Express middleware express.json() is used to parse JSON request bodies automatically.

beginner

How do you parse URL-encoded form data in Express?

Use the middleware express.urlencoded({ extended: true }) to parse URL-encoded form data sent by HTML forms.

intermediate

What does the option extended: true mean in express.urlencoded()?

It allows parsing nested objects in URL-encoded data using the qs library, enabling richer data structures than simple key-value pairs.

beginner

What happens if you try to access req.body without parsing middleware?

The req.body will be undefined or empty because Node.js does not parse the request body by default.

Which middleware should you use to parse JSON bodies in Express?

A express.json()

B express.urlencoded()

C body-parser.text()

D express.static()

express.json() parses incoming JSON request bodies.

To parse form data sent with content-type 'application/x-www-form-urlencoded', which middleware is correct?

A express.raw()

B express.json()

C express.urlencoded({ extended: true })

D express.static()

express.urlencoded() parses URL-encoded form data.

What does the 'extended' option in express.urlencoded() control?

A Whether to parse JSON or not

B Whether to allow nested objects in form data

C Whether to parse cookies

D Whether to serve static files

The 'extended' option controls parsing of nested objects in URL-encoded data.

If you forget to add body parsing middleware, what will req.body contain?

A An empty object or undefined

B Parsed data

C Raw buffer data

D An error object

Without parsing middleware, req.body is empty or undefined.

Which content-type header indicates JSON data in a request?

A text/html

B application/x-www-form-urlencoded

C multipart/form-data

D application/json

application/json is the content-type for JSON data.

Explain how to set up Express middleware to parse both JSON and URL-encoded form data in incoming requests.

Think about the two common content types and how Express handles them.

Describe what happens behind the scenes when Express parses a JSON request body.

Consider how raw data becomes usable JavaScript.

Practice

1. What does express.json() middleware do in a Node.js Express app?

easy

A. It serves static JSON files from the server.

B. It parses URL query parameters and stores them in req.query.

C. It encrypts JSON data before sending it to the client.

D. It parses incoming JSON request bodies and makes the data available in req.body.

Solution

1. Step 1: Understand express.json() purpose

   This middleware parses JSON data sent in the request body, converting it into a JavaScript object.

2. Step 2: Know where parsed data is stored

   The parsed object is assigned to req.body so route handlers can access it easily.

3. Final Answer:

   It parses incoming JSON request bodies and makes the data available in req.body. -> Option D

4. Quick Check:

   express.json() parses JSON body = C [OK]

Hint: express.json() parses JSON body into req.body [OK]

Common Mistakes:

• Confusing express.json() with parsing URL query parameters
• Thinking it serves static files
• Assuming it encrypts data

2. Which middleware correctly parses URL-encoded form data in Express?

easy

A. app.use(express.urlencoded({ extended: true }))

B. app.use(express.json())

C. app.use(express.static('public'))

D. app.use(bodyParser.raw())

Solution

1. Step 1: Identify middleware for form data

   express.urlencoded() parses URL-encoded form data sent by HTML forms.

2. Step 2: Check correct usage

   Using { extended: true } allows rich objects and arrays to be encoded.

3. Final Answer:

   app.use(express.urlencoded({ extended: true })) -> Option A

4. Quick Check:

   express.urlencoded() parses form data = A [OK]

Hint: Use express.urlencoded() for form data parsing [OK]

Common Mistakes:

• Using express.json() for form data
• Confusing static file serving with parsing
• Using bodyParser.raw() instead of urlencoded

3. Given this Express route, what will console.log(req.body) output if the client sends JSON {"name":"Alice"}?

app.use(express.json());
app.post('/user', (req, res) => {
  console.log(req.body);
  res.send('Received');
});

medium

A. { name: 'Alice' }

B. undefined

C. An empty object {}

D. A string '{"name":"Alice"}'

Solution

1. Step 1: Middleware parses JSON body

   express.json() converts JSON string into a JavaScript object and assigns it to req.body.

2. Step 2: Logging req.body shows parsed object

   console.log prints the object { name: 'Alice' }.

3. Final Answer:

   { name: 'Alice' } -> Option A

4. Quick Check:

   express.json() parses JSON to object = B [OK]

Hint: express.json() parses JSON string to object in req.body [OK]

Common Mistakes:

• Expecting req.body to be a string
• Not using express.json() middleware
• Assuming req.body is undefined

4. Why does req.body remain undefined in this Express app?

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

app.post('/submit', (req, res) => {
  console.log(req.body);
  res.send('Done');
});

app.listen(3000);

medium

A. Because the server is not listening on port 3000.

B. Because the route path is incorrect.

C. Because the app is missing middleware to parse the request body.

D. Because console.log cannot print req.body.

Solution

1. Step 1: Check middleware usage

   The app does not use express.json() or express.urlencoded(), so request bodies are not parsed.

2. Step 2: Understand req.body behavior

   Without parsing middleware, req.body is undefined because Express does not parse request bodies by default.

3. Final Answer:

   Because the app is missing middleware to parse the request body. -> Option C

4. Quick Check:

   Missing body parser middleware = D [OK]

Hint: Always add body parser middleware to access req.body [OK]

Common Mistakes:

• Assuming req.body is always available
• Blaming route path or console.log
• Ignoring middleware setup

5. You want to accept both JSON and URL-encoded form data in your Express app. Which setup correctly parses both types so req.body works for all POST requests?

hard

A. app.use(express.urlencoded({ extended: false })); app.use(express.json());

B. app.use(express.json()); app.use(express.urlencoded({ extended: true }));

C. app.use(express.json()); app.use(express.urlencoded({ extended: false }));

D. app.use(bodyParser.json()); app.use(bodyParser.urlencoded());

Solution

1. Step 1: Identify middleware for both data types

   express.json() parses JSON bodies; express.urlencoded({ extended: true }) parses form data with rich objects.

2. Step 2: Confirm correct order and options

   Both middlewares should be used; extended: true allows nested objects in form data.

3. Final Answer:

   app.use(express.json()); app.use(express.urlencoded({ extended: true })); -> Option B

4. Quick Check:

   Use both express.json() and express.urlencoded({ extended: true }) = A [OK]

Hint: Use both express.json() and express.urlencoded({ extended: true }) [OK]

Common Mistakes:

• Using extended: false limits form data parsing
• Using deprecated bodyParser package
• Not including both middlewares