GET route handling in Express

Introduction

GET route handling lets your server respond when someone asks for information. It helps deliver web pages or data when users visit a link.

When you want to show a homepage or a webpage to visitors.

When you need to send data like a list of products to a user.

When a user clicks a link and your server should send back the right content.

When you want to test if your server is running by visiting a simple URL.

When you want to fetch user details by their ID from the URL.

Syntax

Express

app.get('/path', (req, res) => {
  // code to handle the request
  res.send('response')
})

app.get listens for GET requests on the given path.

The callback has req for request info and res to send back a response.

Examples

Sends a welcome message when someone visits the root URL.

Express

app.get('/', (req, res) => {
  res.send('Welcome to the homepage!')
})

Responds with a simple About page text.

Express

app.get('/about', (req, res) => {
  res.send('About us page')
})

Reads a user ID from the URL and sends it back in the response.

Express

app.get('/user/:id', (req, res) => {
  const userId = req.params.id
  res.send(`User ID requested: ${userId}`)
})

Sample Program

This program creates a simple Express server with two GET routes. The root route sends a greeting message. The second route reads a name from the URL and sends a personalized greeting.

Express

import express from 'express'

const app = express()
const port = 3000

app.get('/', (req, res) => {
  res.send('Hello! This is the homepage.')
})

app.get('/greet/:name', (req, res) => {
  const name = req.params.name
  res.send(`Hello, ${name}! Welcome to our site.`)
})

app.listen(port, () => {
  console.log(`Server running at http://localhost:${port}`)
})

Important Notes

GET routes only respond to GET requests, which are usually for getting data or pages.

Use req.params to get dynamic parts of the URL like IDs or names.

Always send a response with res.send(), res.json(), or similar to avoid hanging requests.

Summary

GET route handling lets your server answer requests for pages or data.

Use app.get(path, callback) to define what happens when a URL is visited.

You can read URL parts with req.params to customize responses.

Practice

1. What does the app.get() method do in an Express app?

easy

A. Starts the Express server and listens on a port

B. Defines a route to handle GET requests at a specific URL

C. Sends a POST request to a server

D. Deletes a route from the Express app

Solution

1. Step 1: Understand the purpose of app.get()

   The app.get() method is used to define a route that listens for GET requests on a given URL path.

2. Step 2: Compare with other methods

   Other methods like app.post() handle POST requests, and app.listen() starts the server, so they do not define GET routes.

3. Final Answer:

   Defines a route to handle GET requests at a specific URL -> Option B

4. Quick Check:

   app.get() defines GET routes [OK]

Hint: app.get() always sets up a GET route handler [OK]

Common Mistakes:

• Confusing app.get() with app.listen()
• Thinking app.get() sends requests instead of handling them
• Mixing GET with POST methods

2. Which of the following is the correct syntax to create a GET route for the path /hello that sends "Hello World" as a response?

easy

A. app.get('/hello', (req, res) => { res.send('Hello World'); });

B. app.get('/hello', (res, req) => { res.send('Hello World'); });

C. app.get('/hello', (req, res) => { res.write('Hello World'); });

D. app.get('/hello', (req, res) => { res.sendHello('Hello World'); });

Solution

1. Step 1: Check parameter order in callback

   The callback function parameters must be req first, then res. app.get('/hello', (res, req) => { res.send('Hello World'); }); reverses them, which is incorrect.

2. Step 2: Verify response method usage

   The correct method to send a response string is res.send(). app.get('/hello', (req, res) => { res.write('Hello World'); }); uses res.write() which is not standard in Express, and app.get('/hello', (req, res) => { res.sendHello('Hello World'); }); uses a non-existent method res.sendHello().

3. Final Answer:

   app.get('/hello', (req, res) => { res.send('Hello World'); }); -> Option A

4. Quick Check:

   Correct syntax uses req, res and res.send() [OK]

Hint: Use (req, res) and res.send() to respond in GET routes [OK]

Common Mistakes:

• Swapping req and res parameters
• Using res.write() instead of res.send()
• Calling non-existent response methods

3. What will be the output when a GET request is made to /user/42 with this route handler?

app.get('/user/:id', (req, res) => {
  res.send(`User ID is ${req.params.id}`);
});

medium

A. User ID is undefined

B. User ID is :id

C. Error: req.params is not defined

D. User ID is 42

Solution

1. Step 1: Understand route parameters

   The route /user/:id captures the part after /user/ as req.params.id.

2. Step 2: Substitute parameter in response

   When visiting /user/42, req.params.id is "42", so the response is "User ID is 42".

3. Final Answer:

   User ID is 42 -> Option D

4. Quick Check:

   Route params fill req.params.id correctly [OK]

Hint: Use req.params to get URL parts in routes [OK]

Common Mistakes:

• Using req.params without defining route parameter
• Expecting literal ':id' in output
• Forgetting to use backticks for template strings

4. Identify the error in this GET route handler:

app.get('/data', (req, res) => {
  res.send('Data received')
  res.send('Another response');
});

medium

A. Missing semicolon after first res.send()

B. Route path should be '/data/' with trailing slash

C. Cannot call res.send() twice in the same request handler

D. req parameter is unused and causes error

Solution

1. Step 1: Check response sending rules

   Express allows sending only one response per request. Calling res.send() twice causes an error.

2. Step 2: Analyze other options

   Missing semicolons do not cause runtime errors here, trailing slash is optional, and unused parameters do not cause errors.

3. Final Answer:

   Cannot call res.send() twice in the same request handler -> Option C

4. Quick Check:

   Only one res.send() per request allowed [OK]

Hint: Send response only once per route handler [OK]

Common Mistakes:

• Calling res.send() multiple times
• Thinking missing semicolons cause errors
• Confusing trailing slash necessity

5. You want to create a GET route /product/:category/:id that responds with a message like "Category: electronics, ID: 123". Which code correctly implements this?

hard

A. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); });

B. app.get('/product/:category/:id', (req, res) => { res.send('Category: req.params.category, ID: req.params.id'); });

C. app.get('/product/:category/:id', (res, req) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); });

D. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.query.category}, ID: ${req.query.id}`); });

Solution

1. Step 1: Use correct parameter order and template literals

   The callback must have (req, res) and use backticks with ${} to insert variables. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); }); does this correctly.

2. Step 2: Use req.params for URL parameters

   Route parameters are accessed via req.params, not req.query. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.query.category}, ID: ${req.query.id}`); }); incorrectly uses req.query. app.get('/product/:category/:id', (req, res) => { res.send('Category: req.params.category, ID: req.params.id'); }); uses quotes, so variables won't be evaluated. app.get('/product/:category/:id', (res, req) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); }); swaps parameters.

3. Final Answer:

   app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); }); -> Option A

4. Quick Check:

   Use req.params and template literals correctly [OK]

Hint: Use req.params and backticks for dynamic route responses [OK]

Common Mistakes:

• Swapping req and res parameters
• Using string quotes instead of template literals
• Using req.query instead of req.params for route params