req.method and req.url in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does req.method represent in Express?

req.method is a string that shows the HTTP method used in the request, like GET, POST, PUT, or DELETE.

beginner

What information does req.url provide in an Express request?

req.url gives the path and query string part of the URL the client requested, for example, /home?user=123.

intermediate

How can req.method and req.url be used together in Express?

You can check req.method and req.url to decide how to respond, like handling GET requests to /about differently from POST requests to /submit.

beginner

Example: What will req.method and req.url be if a user visits POST /login?

req.method will be "POST" and req.url will be "/login".

beginner

Why is it useful to check req.method in your Express app?

Because it helps your app know what the client wants to do, like get data, send data, update, or delete something, so you can respond correctly.

What does req.method contain in an Express request?

A The response status code

B The full URL including domain

C The request headers

D The HTTP method like GET or POST

req.method holds the HTTP method used by the client, such as GET or POST.

If a user visits http://example.com/products?item=5, what will req.url be?

A /products?item=5

B http://example.com/products?item=5

C /products

D item=5

req.url contains the path and query string, so it will be /products?item=5.

Which of these is true about req.method and req.url?

A Both contain the full URL

B <code>req.method</code> is the URL path, <code>req.url</code> is the HTTP method

C <code>req.method</code> is the HTTP method, <code>req.url</code> is the URL path and query

D Both contain HTTP headers

req.method is the HTTP method, and req.url is the path plus query string.

Why might you check req.method in your Express route handler?

A To know what kind of request the client sent

B To get the client's IP address

C To read cookies

D To set response headers

Checking req.method tells you if the client wants to get, post, or delete data.

What will req.url be if the user requests GET /search?q=books?

A GET

B /search?q=books

C /search

D books

req.url includes the path and query string, so it will be /search?q=books.

Explain what req.method and req.url represent in an Express request and how you might use them.

Think about how your app knows what the client wants and where.

Describe a simple example where checking req.method and req.url helps your Express app respond differently.

Imagine a website with a home page and a form submission.

Practice

1. What does req.method represent in an Express request?

easy

A. The HTTP method used by the client (e.g., GET, POST)

B. The full URL including domain name

C. The IP address of the client

D. The server's response status code

Solution

1. Step 1: Understand the purpose of req.method

   req.method holds the HTTP method used by the client to make the request, such as GET, POST, PUT, DELETE.

2. Step 2: Differentiate from other request properties

   req.url gives the path and query, IP address is separate, and response status is not part of the request object.

3. Final Answer:

   The HTTP method used by the client (e.g., GET, POST) -> Option A

4. Quick Check:

   req.method = HTTP method [OK]

Hint: Remember: method means action type like GET or POST [OK]

Common Mistakes:

• Confusing req.method with req.url
• Thinking req.method gives client IP
• Assuming req.method is server response code

2. Which of the following is the correct way to check if a request is a POST method in Express?

easy

A. if (req.url === 'POST')

B. if (req.url === '/post')

C. if (req.method = 'POST')

D. if (req.method === 'POST')

Solution

1. Step 1: Identify the property holding HTTP method

   The HTTP method is stored in req.method, so we compare it to the string 'POST'.

2. Step 2: Check syntax correctness

   if (req.method === 'POST') uses strict equality (===) to compare req.method to 'POST', which is correct. if (req.method = 'POST') uses assignment (=) which is wrong.

3. Final Answer:

   if (req.method === 'POST') -> Option D

4. Quick Check:

   Check req.method with === 'POST' [OK]

Hint: Use === to compare req.method with 'POST' string [OK]

Common Mistakes:

• Using assignment (=) instead of comparison (===)
• Checking req.url instead of req.method
• Comparing req.method to lowercase 'post'

3. Given this Express code snippet, what will be logged if a client sends a GET request to /home?user=123?

app.use((req, res, next) => {
  console.log(req.method);
  console.log(req.url);
  next();
});

medium

A. GET
/home?user=123

B. POST
/home?user=123

C. GET
/home

D. POST
/home

Solution

1. Step 1: Identify the HTTP method from the request

   The client sends a GET request, so req.method will be 'GET'.

2. Step 2: Identify the URL including query string

   req.url includes the path and query string, so it will be '/home?user=123'.

3. Final Answer:

   GET /home?user=123 -> Option A

4. Quick Check:

   req.method = GET, req.url includes query [OK]

Hint: req.url includes path plus query string [OK]

Common Mistakes:

• Ignoring query string in req.url
• Assuming req.method is POST by default
• Confusing req.url with just the path

4. What is wrong with this Express middleware code if it aims to log only POST requests?

app.use((req, res, next) => {
  if (req.method = 'POST') {
    console.log('POST request received');
  }
  next();
});

medium

A. Missing parentheses around req.method

B. Using assignment (=) instead of comparison (===) in the if condition

C. Logging message is incorrect

D. next() is called before the if condition

Solution

1. Step 1: Check the if condition syntax

   The condition uses = which assigns 'POST' to req.method instead of comparing it. This causes a bug.

2. Step 2: Identify correct comparison operator

   Use === to compare values in JavaScript, so the condition should be req.method === 'POST'.

3. Final Answer:

   Using assignment (=) instead of comparison (===) in the if condition -> Option B

4. Quick Check:

   Use === for comparison, not = [OK]

Hint: Use === to compare, not = which assigns [OK]

Common Mistakes:

• Using = instead of === in if condition
• Thinking next() must be before if
• Assuming parentheses needed around req.method

5. You want to create an Express middleware that logs a message only when the client requests the URL /api/data with a GET method. Which code snippet correctly implements this?

hard

A. app.use((req, res, next) => {
if (req.method === 'POST' && req.url === '/api/data') {
console.log('GET request to /api/data');
}
next();
});

B. app.use((req, res, next) => {
if (req.method = 'GET' || req.url === '/api/data') {
console.log('GET request to /api/data');
}
next();
});

C. app.use((req, res, next) => {
if (req.method === 'GET' && req.url === '/api/data') {
console.log('GET request to /api/data');
}
next();
});

D. app.use((req, res, next) => {
if (req.method === 'GET' && req.url === '/api') {
console.log('GET request to /api/data');
}
next();
});

Solution

1. Step 1: Check method and URL conditions

   The middleware should check if req.method is exactly 'GET' and req.url is exactly '/api/data'.

2. Step 2: Verify logical operators and syntax

   app.use((req, res, next) => { if (req.method === 'GET' && req.url === '/api/data') { console.log('GET request to /api/data'); } next(); }); uses strict equality (===) and logical AND (&&) correctly. app.use((req, res, next) => { if (req.method = 'GET' || req.url === '/api/data') { console.log('GET request to /api/data'); } next(); }); uses assignment (=) and OR (||) which is wrong. Options C and D check wrong method or URL.

3. Final Answer:

   app.use((req, res, next) => { if (req.method === 'GET' && req.url === '/api/data') { console.log('GET request to /api/data'); } next(); }); -> Option C

4. Quick Check:

   Check req.method === 'GET' AND req.url === '/api/data' [OK]

Hint: Use === and && to check method and exact URL [OK]

Common Mistakes:

• Using = instead of ===
• Using || instead of &&
• Checking wrong URL or method