Query string parsing in Express - Step-by-Step Execution

Concept Flow - Query string parsing

Client sends URL with query string

↓

Express receives request

↓

Express parses URL

↓

Extract query string part

↓

Parse query string into key-value pairs

↓

Make parsed query available as req.query

↓

Route handler uses req.query values

Express takes the URL from the client, extracts the query string, parses it into an object, and makes it available as req.query for your code to use.

Execution Sample

Express

app.get('/search', (req, res) => {
  const term = req.query.term;
  res.send(`You searched for: ${term}`);
});

This code reads the 'term' parameter from the query string and sends a response showing what was searched.

Execution Table

Step	Action	Input URL	Parsed Query Object	Output
1	Client sends request	/search?term=books&sort=asc	N/A	N/A
2	Express receives request	/search?term=books&sort=asc	N/A	N/A
3	Express parses URL	/search?term=books&sort=asc	N/A	N/A
4	Extract query string	/search?term=books&sort=asc	{ term: 'books', sort: 'asc' }	N/A
5	Make query available as req.query	/search?term=books&sort=asc	{ term: 'books', sort: 'asc' }	N/A
6	Route handler reads req.query.term	/search?term=books&sort=asc	{ term: 'books', sort: 'asc' }	term = 'books'
7	Send response	/search?term=books&sort=asc	{ term: 'books', sort: 'asc' }	You searched for: books

💡 Request handled and response sent with parsed query string values.

Variable Tracker

Variable	Start	After Step 4	After Step 6	Final
req.query	undefined	{ term: 'books', sort: 'asc' }	{ term: 'books', sort: 'asc' }	{ term: 'books', sort: 'asc' }
term	undefined	undefined	'books'	'books'

Key Moments - 3 Insights

Why is req.query an object and not a string?

Because Express automatically parses the query string into an object with keys and values, as shown in step 4 and 5 of the execution_table.

What happens if the query string is empty or missing?

req.query will be an empty object {}, so accessing any key like req.query.term will be undefined, as no query parameters exist.

Can query string values be accessed directly without parsing?

No, Express parses the query string for you. You must use req.query to access parameters, not the raw URL string.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of req.query after step 4?

A undefined

B { term: 'books', sort: 'asc' }

C string '/search?term=books&sort=asc'

D null

💡 Hint

Check the 'Parsed Query Object' column at step 4 in the execution_table.

At which step does the route handler read the 'term' parameter from the query?

A Step 6

B Step 2

C Step 3

D Step 5

💡 Hint

Look for the step where 'term' is assigned a value in the execution_table.

If the URL was '/search' with no query string, what would req.query be?

A undefined

B null

C {} (empty object)

D { term: undefined }

💡 Hint

Refer to the key_moments section about empty or missing query strings.

Concept Snapshot

Express parses the query string from the URL automatically.
Parsed query parameters are available as an object in req.query.
Access parameters by their key names, e.g., req.query.term.
If no query string, req.query is an empty object {}.
Use req.query inside route handlers to get user input from URLs.

Full Transcript

When a client sends a URL with a query string, Express receives the request and parses the URL. It extracts the query string part after the question mark and converts it into an object with key-value pairs. This object is stored in req.query. Inside your route handler, you can access these parameters by their keys, like req.query.term. If the query string is missing, req.query will be an empty object. This process lets you easily get user input from URLs without manual parsing.

Practice

1. In Express, which object lets you access the query parameters from a URL like /search?term=books?

easy

A. req.query

B. req.params

C. req.body

D. req.url

Solution

1. Step 1: Understand Express request objects

   Express provides different objects to access parts of the request: req.params for route params, req.body for POST data, and req.query for query strings.

2. Step 2: Identify query string access

   The query string is the part after ? in a URL. Express parses it into req.query as an object.

3. Final Answer:

   req.query -> Option A

4. Quick Check:

   Query string = req.query [OK]

Hint: Query strings are in req.query object in Express [OK]

Common Mistakes:

• Confusing req.params with req.query
• Trying to read query from req.body
• Using req.url directly without parsing

2. Which of the following is the correct way to read a query parameter named page in an Express route handler?

easy

A. const page = req.query.page;

B. const page = req.body.page;

C. const page = req.params.page;

D. const page = req.url.page;

Solution

1. Step 1: Recall query parameter access syntax

   Query parameters are accessed via req.query as key-value pairs.

2. Step 2: Match correct syntax

   To get the page parameter, use req.query.page. Other options access wrong objects.

3. Final Answer:

   const page = req.query.page; -> Option A

4. Quick Check:

   Query param 'page' = req.query.page [OK]

Hint: Use req.query.paramName to get query parameters [OK]

Common Mistakes:

• Using req.params for query parameters
• Trying to read query from req.body
• Accessing req.url.page which is undefined

3. Given this Express route handler:

app.get('/items', (req, res) => {
  const limit = Number(req.query.limit) || 10;
  res.send(`Limit is ${limit}`);
});

What will be the response if the URL is /items?limit=5?

medium

A. "Limit is 10"

B. "Limit is undefined"

C. "Limit is 5"

D. "Limit is NaN"

Solution

1. Step 1: Convert query string value to number

   The code uses Number(req.query.limit) to convert the string '5' to number 5.

2. Step 2: Use default if conversion fails

   If conversion results in 0 or NaN, it defaults to 10. Here, 5 is valid, so limit = 5.

3. Final Answer:

   "Limit is 5" -> Option C

4. Quick Check:

   Number('5') = 5, so output = "Limit is 5" [OK]

Hint: Convert query strings to number before use [OK]

Common Mistakes:

• Not converting string to number
• Assuming req.query.limit is a number
• Ignoring default fallback logic

4. Consider this Express route:

app.get('/search', (req, res) => {
  const term = req.query.term.toLowerCase();
  res.send(term);
});

What error will occur if the URL is /search (no query parameter)?

medium

A. SyntaxError: Unexpected token

B. TypeError: Cannot read property 'toLowerCase' of undefined

C. ReferenceError: term is not defined

D. No error, response is empty string

Solution

1. Step 1: Check for missing query parameter

   If term is missing, req.query.term is undefined.

2. Step 2: Calling method on undefined causes error

   Calling toLowerCase() on undefined throws a TypeError.

3. Final Answer:

   TypeError: Cannot read property 'toLowerCase' of undefined -> Option B

4. Quick Check:

   Undefined.toLowerCase() throws TypeError [OK]

Hint: Check if query param exists before using methods [OK]

Common Mistakes:

• Assuming query param always exists
• Not handling undefined values
• Expecting empty string instead of error

5. You want to handle a query parameter sort that can be either asc or desc. If missing or invalid, default to asc. Which code snippet correctly implements this in Express?

hard

A. const sort = req.query.sort === 'asc' ? 'asc' : req.query.sort === 'desc' ? 'desc' : 'desc';

B. const sort = req.query.sort || 'asc';

C. const sort = req.query.sort === 'asc' ? 'asc' : 'desc';

D. const sort = ['asc', 'desc'].includes(req.query.sort) ? req.query.sort : 'asc';

Solution

1. Step 1: Validate query parameter value

   We must check if req.query.sort is either 'asc' or 'desc'. Using includes() on an array is a clean way.

2. Step 2: Provide default if invalid or missing

   If the value is not in the allowed list, default to 'asc'. This avoids invalid values.

3. Final Answer:

   const sort = ['asc', 'desc'].includes(req.query.sort) ? req.query.sort : 'asc'; -> Option D

4. Quick Check:

   Check allowed values with includes() and default [OK]

Hint: Use includes() to validate query param values before use [OK]

Common Mistakes:

• Not validating allowed values
• Using simple || which accepts invalid strings
• Overcomplicating with nested ternaries