Why building HTTP servers matters in Node.js - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do we use HTTP servers in Node.js?

Which of the following best explains why building HTTP servers is important in Node.js?

A HTTP servers are only used to send emails from Node.js.

B HTTP servers allow Node.js to listen for and respond to web requests, enabling web applications to work.

C HTTP servers are used to store files on the computer permanently.

D HTTP servers help Node.js to run desktop applications faster.

💡 Hint

Think about what happens when you open a website in your browser.

HTTP servers listen for requests from browsers or other clients and send back responses like web pages or data. This is how websites and web apps work.

❓ component_behavior

intermediate

What happens when a Node.js HTTP server receives a request?

Consider a simple Node.js HTTP server. What does the server do when it receives a request from a browser?

A It processes the request and sends back a response like a web page or data.

B It immediately shuts down to save resources.

C It ignores the request and waits for a different type of input.

D It sends the request to the operating system to handle.

💡 Hint

Think about what a web server's job is when you visit a website.

The server listens for requests, processes them, and sends back responses so the browser can show the web page or data.

📝 Syntax

advanced

Identify the correct way to create a basic HTTP server in Node.js

Which code snippet correctly creates a simple HTTP server that responds with 'Hello World'?

Node.js

const http = require('http');

// Choose the correct server creation code below

A const server = http.createServer((req, res) => { res.write('Hello World'); res.end(); });

B const server = http.createServer((req, res) => { res.send('Hello World'); });

C const server = http.createServer((request, response) => { response.writeHead(200); response.end('Hello World'); });

D const server = http.createServer((req, res) => { res.write('Hello World'); })

💡 Hint

Remember to send a status code and end the response properly.

Option C correctly sets the status code with writeHead and ends the response with the message. Option C misses the status code. Option C uses a method not available on the response object. Option C does not end the response, so the client waits forever.

🔧 Debug

advanced

Why does this Node.js HTTP server code cause the browser to hang?

Look at this code snippet: const http = require('http'); const server = http.createServer((req, res) => { res.write('Loading...'); }); server.listen(3000); Why does the browser keep loading and never show the response?

A Because the callback function is missing the request parameter.

B Because the server.listen port is incorrect.

C Because res.write() cannot be used in HTTP servers.

D Because res.end() is missing, so the response never finishes.

💡 Hint

Think about how HTTP responses are completed.

The response must be ended with res.end() to tell the browser the message is complete. Without it, the browser waits forever.

❓ state_output

expert

What is the output when multiple requests hit this Node.js HTTP server?

Consider this server code: const http = require('http'); let count = 0; const server = http.createServer((req, res) => { count++; res.writeHead(200, {'Content-Type': 'text/plain'}); res.end(`Request number: ${count}`); }); server.listen(3000); If three requests come in one after another, what will the third request receive as a response?

A "Request number: 3"

B "Request number: 1"

C "Request number: 0"

D An error because count is not reset

💡 Hint

Think about how the variable count changes with each request.

The variable count increments with each request, so the third request gets the value 3.

Practice

1. Why is building an HTTP server important in Node.js?

easy

A. It automatically fixes bugs in your code.

B. It makes your computer run faster.

C. It allows your computer to share information over the internet.

D. It helps you write desktop applications.

Solution

1. Step 1: Understand the role of HTTP servers

   HTTP servers let computers send and receive information over the internet.

2. Step 2: Connect this to Node.js usage

   Node.js provides tools to build these servers so your app can communicate online.

3. Final Answer:

   It allows your computer to share information over the internet. -> Option C

4. Quick Check:

   HTTP servers = share info online [OK]

Hint: HTTP servers share info online, not speed or desktop apps [OK]

Common Mistakes:

• Thinking HTTP servers speed up the computer
• Confusing servers with desktop app tools
• Believing servers fix code bugs automatically

2. Which of the following is the correct way to create a basic HTTP server in Node.js using ES modules?

easy

A. import http from 'http'; http.createServer((req, res) => res.end('Hello')).listen(3000);

B. const http = require('http'); http.createServer((req, res) => res.end('Hello')).listen(3000);

C. const http = import('http'); http.createServer((req, res) => res.end('Hello')).listen(3000);

D. const http = require('http'); http.createServer((req, res) => res.send('Hello')).listen(3000);

Solution

1. Step 1: Identify modern Node.js import syntax

   Node.js ES modules use import to load modules, not require.

2. Step 2: Check server creation and response method

   http.createServer with res.end() is correct; res.send() is not a Node.js method.

3. Final Answer:

   import http from 'http'; http.createServer((req, res) => res.end('Hello')).listen(3000); -> Option A

4. Quick Check:

   Use import + res.end() in Node.js 20+ [OK]

Hint: Use import and res.end() for Node.js HTTP servers [OK]

Common Mistakes:

• Using require instead of import in ES modules
• Using res.send() which is not in Node.js core
• Trying to import with const and import() function

3. What will this Node.js HTTP server print when accessed?

import http from 'http';
const server = http.createServer((req, res) => {
  res.statusCode = 200;
  res.setHeader('Content-Type', 'text/plain');
  res.end('Welcome!');
});
server.listen(3000);

medium

A. Error: statusCode is not a property

B. Welcome!

C. undefined

D. Content-Type header missing

Solution

1. Step 1: Analyze server response setup

   The server sets status code 200, sets Content-Type header, and ends response with 'Welcome!'.

2. Step 2: Understand what client receives

   The client will get a plain text response with 'Welcome!' and status 200.

3. Final Answer:

   Welcome! -> Option B

4. Quick Check:

   res.end('Welcome!') sends text response [OK]

Hint: res.end sends the response body text [OK]

Common Mistakes:

• Thinking statusCode is invalid property
• Expecting undefined instead of response text
• Ignoring headers set by setHeader

4. Identify the error in this Node.js HTTP server code:

import http from 'http';
const server = http.createServer((req, res) => {
  res.write('Hello');
  res.write('World');
  res.end();
});
server.listen(3000);

medium

A. No error, code works fine

B. Cannot call res.write multiple times

C. Missing res.end() call

D. res.end() should have a string argument

Solution

1. Step 1: Review usage of res.write and res.end

   Node.js allows multiple res.write calls before res.end to send chunks.

2. Step 2: Confirm res.end usage

   Calling res.end() without argument is valid; it ends the response.

3. Final Answer:

   No error, code works fine -> Option A

4. Quick Check:

   Multiple res.write calls + res.end() is valid [OK]

Hint: Multiple res.write calls are allowed before res.end [OK]

Common Mistakes:

• Thinking res.end must have argument
• Believing multiple res.write calls cause error
• Forgetting res.end is needed to finish response

5. You want to build a Node.js HTTP server that responds with JSON data and handles errors gracefully. Which approach is best?

hard

A. Use http.createServer, set Content-Type to application/json, but do not handle errors.

B. Use http.createServer, send JSON as plain text, ignore errors to keep server fast.

C. Use http.createServer, set Content-Type to text/html, and send JSON string directly.

D. Use http.createServer, set Content-Type to application/json, and wrap response code in try-catch.

Solution

1. Step 1: Set correct Content-Type for JSON

   To send JSON, Content-Type must be 'application/json' so clients parse it properly.

2. Step 2: Handle errors gracefully

   Wrapping response code in try-catch prevents server crashes and sends error info.

3. Final Answer:

   Use http.createServer, set Content-Type to application/json, and wrap response code in try-catch. -> Option D

4. Quick Check:

   JSON needs correct header + error handling [OK]

Hint: Always set JSON header and catch errors in server code [OK]

Common Mistakes:

• Sending JSON with wrong Content-Type
• Ignoring errors causing server crashes
• Using text/html header for JSON data