Parsing request body (JSON and form data) in Node.js - Step-by-Step Execution

Concept Flow - Parsing request body (JSON and form data)

Client sends HTTP request

↓

Server receives request

↓

Check Content-Type header

↓

Parse JSON body

↓

Store parsed data in req.body

↓

Use req.body in route handler

↓

Send response

The server checks the request's Content-Type to decide how to parse the body, then stores the parsed data for use in the route.

Execution Sample

Node.js

import express from 'express';
const app = express();
app.use(express.json());
app.use(express.urlencoded({ extended: true }));
app.post('/submit', (req, res) => {
  res.json(req.body);
});

This code sets up an Express server that parses JSON and form data bodies, then echoes back the parsed data.

Execution Table

Step	Action	Content-Type	Parsing Method	req.body Content	Response Sent
1	Receive POST /submit	application/json	Check Content-Type	{}	No
2	Parse body	application/json	express.json() middleware	{"name":"Alice"}	No
3	Route handler runs	application/json	Use req.body	{"name":"Alice"}	No
4	Send response	application/json	Send JSON response	{"name":"Alice"}	Yes
5	Receive POST /submit	application/x-www-form-urlencoded	Check Content-Type	{}	No
6	Parse body	application/x-www-form-urlencoded	express.urlencoded() middleware	{"name":"Bob","age":"30"}	No
7	Route handler runs	application/x-www-form-urlencoded	Use req.body	{"name":"Bob","age":"30"}	No
8	Send response	application/x-www-form-urlencoded	Send JSON response	{"name":"Bob","age":"30"}	Yes
9	Receive POST /submit	text/plain	Check Content-Type	{}	No
10	Parse body	text/plain	No parser matches	{}	No
11	Route handler runs	text/plain	req.body empty	{}	No
12	Send response	text/plain	Send JSON response	{}	Yes

💡 Parsing stops after sending response or when no matching parser is found.

Variable Tracker

Variable	Start	After Step 2	After Step 6	After Step 10	Final
req.body	{}	{"name":"Alice"}	{"name":"Bob","age":"30"}	{}	{}

Key Moments - 3 Insights

Why is req.body empty when Content-Type is text/plain?

Because express.json() and express.urlencoded() only parse JSON and form data. No parser runs for text/plain, so req.body stays empty as shown in steps 9-11.

How does the server know which parser to use?

The server checks the Content-Type header (step 1 and 5). If it is application/json, express.json() parses the body. If it is application/x-www-form-urlencoded, express.urlencoded() parses it.

Why is age a string in req.body after form data parsing?

Form data values are always strings by default, so age is "30" as a string, not a number, as seen in step 7.

Visual Quiz - 3 Questions

Look at the execution table, what is req.body content after step 6?

A {"name":"Bob","age":"30"}

B {"name":"Alice"}

C {}

D null

💡 Hint

Check the 'req.body Content' column at step 6 in the execution_table.

At which step does the server send the response for a JSON request?

A Step 3

B Step 4

C Step 2

D Step 1

💡 Hint

Look for 'Response Sent' marked 'Yes' for application/json in the execution_table.

If the Content-Type was missing, what would req.body be?

A null

B {"name":"Alice"}

C {}

D undefined

💡 Hint

Refer to steps where no matching parser runs and req.body remains empty.

Concept Snapshot

Parsing request body in Node.js with Express:
- Use express.json() to parse JSON bodies.
- Use express.urlencoded({ extended: true }) to parse form data.
- Server checks Content-Type header to pick parser.
- Parsed data is stored in req.body.
- If Content-Type is unsupported, req.body is empty.
- Use req.body in route handlers to access client data.

Full Transcript

When a client sends a POST request, the server first checks the Content-Type header to decide how to parse the body. If the Content-Type is application/json, the express.json() middleware parses the JSON string into a JavaScript object and stores it in req.body. If the Content-Type is application/x-www-form-urlencoded, the express.urlencoded() middleware parses the form data string into an object with string values and stores it in req.body. If the Content-Type is unsupported, no parser runs and req.body remains empty. The route handler then uses req.body to access the parsed data and sends it back as a JSON response. This process ensures the server understands the client's data format and can work with it easily.