Creating a basic HTTP server in Node.js - Quick Revision & Summary

Recall & Review

beginner

What Node.js module is used to create a basic HTTP server?

The http module is used to create a basic HTTP server in Node.js.

beginner

What method starts the server and listens for requests?

The server.listen(port, callback) method starts the server and listens on the specified port.

beginner

In the callback for http.createServer(), what are the two main objects provided?

The callback receives request and response objects. request contains info about the incoming request, and response is used to send data back to the client.

beginner

How do you send a plain text response 'Hello World' to the client?

Use response.writeHead(200, {'Content-Type': 'text/plain'}) to set status and headers, then response.end('Hello World') to send the response and close the connection.

beginner

Why is it important to call response.end() in a Node.js HTTP server?

Calling response.end() signals that the response is complete. Without it, the client will keep waiting and the connection stays open.

Which Node.js module do you import to create an HTTP server?

A http

B fs

C path

D url

The http module provides the tools to create an HTTP server.

What method do you use to start listening for incoming requests?

A server.start()

B http.createServer()

C server.listen()

D http.listen()

The listen() method starts the server and listens on a specified port.

In the server callback, which object contains information about the client's request?

A server

B request

C response

D client

The request object holds details about the incoming client request.

How do you send a response header with status 200 and content type 'text/plain'?

A response.writeHead(200, {'Content-Type': 'text/plain'})

B response.write('200', 'text/plain')

C response.setHeader(200, 'text/plain')

D response.sendHeader(200, 'text/plain')

Use writeHead to set status and headers before sending the response body.

What happens if you forget to call response.end()?

A The server crashes

B The server restarts

C The response is sent automatically

D The client keeps waiting and connection stays open

Without response.end(), the server does not finish the response, so the client waits indefinitely.

Explain how to create a basic HTTP server in Node.js that responds with 'Hello World'.

Think about the steps from importing to sending a response and listening on a port.

Describe the roles of the request and response objects in a Node.js HTTP server.

Consider what each object lets you do during a client-server interaction.

Practice

1. What does the http.createServer() function do in Node.js?

easy

A. It compiles JavaScript code into machine code.

B. It creates a database connection for storing data.

C. It creates a server that listens for HTTP requests and sends responses.

D. It formats JSON data for sending over the network.

Solution

1. Step 1: Understand the purpose of http.createServer()

   This function sets up a server that waits for HTTP requests from clients like browsers.

2. Step 2: Identify what the server does

   The server uses a function to handle incoming requests and send back responses, enabling communication over the web.

3. Final Answer:

   It creates a server that listens for HTTP requests and sends responses. -> Option C

4. Quick Check:

   HTTP server creation = It creates a server that listens for HTTP requests and sends responses. [OK]

Hint: Remember: createServer sets up the web server [OK]

Common Mistakes:

• Confusing server creation with database connection
• Thinking it compiles code
• Mixing up data formatting with server setup

2. Which of the following is the correct way to start a Node.js HTTP server on port 3000?

easy

A. http.listen(3000);

B. server.listen(3000);

C. server.start(3000);

D. server.run(3000);

Solution

1. Step 1: Identify the method to start the server

   The correct method to make the server listen on a port is listen().

2. Step 2: Match the method with the server object

   Calling server.listen(3000); starts the server on port 3000.

3. Final Answer:

   server.listen(3000); -> Option B

4. Quick Check:

   Start server with listen() = server.listen(3000); [OK]

Hint: Use listen() to start the server on a port [OK]

Common Mistakes:

• Using non-existent methods like start() or run()
• Calling listen() on http instead of server
• Confusing server methods with other modules

3. What will the following Node.js code output when accessed via a browser?

const http = require('http');
const server = http.createServer((req, res) => {
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.end('Hello World');
});
server.listen(4000);

medium

A. Hello World

B. Error: server.listen is not a function

C. 404 Not Found

D. Hello

Solution

1. Step 1: Analyze the server response setup

   The server sets the HTTP status to 200 (OK) and content type to plain text, then sends 'Hello World' as the response body.

2. Step 2: Understand what the browser receives

   When accessed, the browser will display the exact string 'Hello World' from the server response.

3. Final Answer:

   Hello World -> Option A

4. Quick Check:

   Response text = Hello World [OK]

Hint: Check res.end() content for output text [OK]

Common Mistakes:

• Expecting an error due to incorrect method
• Confusing status codes with output text
• Assuming partial output without reading res.end()

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

const http = require('http');
const server = http.createServer((req, res) => {
  res.writeHead(200, {'Content-Type': 'text/html'});
  res.write('Welcome');
  res.end();
});
server.listen(8080)
console.log('Server running on port 8080');

medium

A. Incorrect Content-Type header value

B. Using res.write() without res.end() causes error

C. Missing semicolon after server.listen(8080)

D. No error; code runs correctly and serves 'Welcome'

Solution

1. Step 1: Check syntax and method usage

   The code correctly calls res.write() followed by res.end(), which is valid to send response data.

2. Step 2: Verify headers and server start

   The Content-Type is valid as 'text/html', and server.listen(8080) starts the server properly. Missing semicolons are optional in JavaScript.

3. Final Answer:

   No error; code runs correctly and serves 'Welcome' -> Option D

4. Quick Check:

   Valid server code = No error; code runs correctly and serves 'Welcome' [OK]

Hint: res.write() + res.end() is valid to send response [OK]

Common Mistakes:

• Thinking missing semicolons cause errors
• Believing res.write() must be avoided
• Assuming wrong Content-Type causes failure

5. You want to create a Node.js HTTP server that responds with JSON data {"status":"ok"} and sets the correct header. Which code snippet correctly does this?

hard

A. const server = http.createServer((req, res) => {
res.writeHead(200, {'Content-Type': 'application/json'});
res.end(JSON.stringify({status: 'ok'}));
});

B. const server = http.createServer((req, res) => {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('{"status":"ok"}');
});

C. const server = http.createServer((req, res) => {
res.writeHead(404, {'Content-Type': 'application/json'});
res.end(JSON.stringify({status: 'ok'}));
});

D. const server = http.createServer((req, res) => {
res.writeHead(200);
res.end({status: 'ok'});
});

Solution

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

   The header must be 'application/json' to tell the client the response is JSON data.

2. Step 2: Send JSON string as response body

   Use JSON.stringify() to convert the object to a JSON string before sending with res.end().

3. Final Answer:

   Code snippet with application/json header and JSON.stringify() -> Option A

4. Quick Check:

   JSON header + stringified data = const server = http.createServer((req, res) => { res.writeHead(200, {'Content-Type': 'application/json'}); res.end(JSON.stringify({status: 'ok'})); }); [OK]

Hint: Use application/json header and JSON.stringify() [OK]

Common Mistakes:

• Sending object directly without stringifying
• Using wrong Content-Type header
• Sending JSON string with text/plain header
• Using 404 status instead of 200