Node.js-based Web Server supporting multiple path

CK CK 3788 
Created at  
603 0 0

Here's a basic example of a Node.js HTTP server that supports multiple paths. This server will respond differently based on the requested URL path.

 

const http = require('http');

// Create an HTTP server
const server = http.createServer((req, res) => {
  // Extract the URL path
  const url = req.url;

  // Set the response header content type
  res.setHeader('Content-Type', 'text/plain');

  // Handle different paths
  if (url === '/') {
    res.writeHead(200);
    res.end('Welcome to the Home Page!');
  } else if (url === '/about') {
    res.writeHead(200);
    res.end('This is the About Page.');
  } else if (url === '/contact') {
    res.writeHead(200);
    res.end('This is the Contact Page.');
  } else {
    res.writeHead(404);
    res.end('404 Not Found');
  }
});

// Specify the port the server should listen on
const port = 3000;
server.listen(port, () => {
  console.log(`Server is running on http://localhost:${port}`);
});

 

How This Works:

  1. Importing the HTTP Module: The http module is used to create an HTTP server.
  2. Creating the Server: The http.createServer() function creates a server object. The function passed to createServer() is executed every time the server gets a request. The req object contains information about the request, such as the URL, while the res object is used to send a response.
  3. Routing: The server checks the req.url to determine the path requested by the client. It then sends different responses based on the path:
    • /: Responds with "Welcome to the Home Page!"
    • /about: Responds with "This is the About Page."
    • /contact: Responds with "This is the Contact Page."
    • Any other path results in a 404 Not Found response.
  4. Starting the Server: The server listens on port 3000. When it starts, it logs a message to the console indicating the server's URL.

 

Running the Server:

  1. Save the code to a file, for example, server.js.
  2. Run the server using Node.js:

    node server.js
    
  3. Open your browser and go to:
    • http://localhost:3000/ for the home page.
    • http://localhost:3000/about for the about page.
    • http://localhost:3000/contact for the contact page.
    • Any other path will show the 404 Not Found message.

 

This example demonstrates how to create a basic HTTP server in Node.js that handles multiple routes, providing a foundation for building more complex applications.

Tags Node.js Web Server Web Server createServer() Facebook X
Comments 0
Similar posts
  1. Multi-threaded Web Server based in Node.js
    866
  2. A basic HTTP server based in Node.js
    544
  3. "502 Bad Gateway" Error easy to happen at the combination of nginx and node.js in AWS Elastic Beanstalk
    10,495
  4. Uvicorn, Gunicorn: Proving Your Production Prowess
    401
  1. Get client IP address and user agent in Node.js
    1,531
  2. forEach method in JavaScript when working with arrays
    667
  3. CRC32B function code in Javascript
    1,844
  4. A simple Javascript class example with static method for Node.js
    661
  5. Setting a Common Path for require() in Node.js
    1,007
  6. Import all JS files in a specific folder for Node.js programming
    1,732
  7. A simple example to access a PostgreSQL database in Node.js
    1,101
  8. Node.js code example to access Google BigQuery
    1,183
  9. Investigation on package.js for Node.js source code
    824
  10. Using MySQL in Node.js
    484
  11. A Node.js script that checks if a module is installed before requiring it
    774
  12. Worker Threads and Mutual Exclusion in Node.js
    466
  13. Using a module in the external class itself without creating an instance in Node.js
    350
  14. Node.js external modules
    434
Recently updated
  1. Google OAuth Token Expiration: Causes and Solutions
    31
  2. Why 100% SEO Guarantees Better User Engagement and How to Achieve It in Your Service
    57
  3. Why SPF and DKIM Are Essential for Linux Email Servers?
    51
  4. How do I create animated background for Google Meet?
    23,222
  5. MaxMind GeoLite2 vs. DB-IP Lite vs. ip-api.com: Choosing the Right Free IP Geolocation Solution
    273
  6. Meet Valkey: Why Redis Changed Its License, Why Valkey is Better, and How to Use It as a Drop-in Replacement
    104
  7. How Rogue Web Scrapers Are Stealing My Content and Destroying My Server
    170
  8. Array of arguments passed to script in PHP
    99
  9. Invalid Auction Storms in Ad Tech
    107
  10. Building MRC-Compliant Instrumentation in Ad Tech: Implementation Steps and Key Challenges
    208
  11. The Two Clocks of Ad Server Architecture
    78
  12. Frequency Cap Architecture Overview
    527
  13. Collecting Proof-of-Play from 100,000 Screens
    153
  14. Vector Search in Relational Databases (RDBs): Trends & Usage Environments
    303
  15. What is RedisVL?
    116
  16. Designing a Skill Registry Architecture: Minimize Token Usage and Maximize AI Performance
    247
  17. TPU & GPU Cluster Management Tools
    258
  18. The Concept of Scaffolding in AI Agents
    245
  19. Beyond Static Pipelines: Architecting LLM Multi-Agent Systems for Autonomous Workflow Orchestration
    598
  20. AI-DLC vs. AI-SDLC: Model-Centric vs. System-Centric AI Development
    268
  21. Fine-Tuning Open-Weight LLMs: Training, Licensing, and Deploying Custom Models with Ollama
    354
  22. Inside the Next-Generation Streaming Architecture: Ultra-Low Latency, SGAI, and AI Codecs
    207
  23. Machine Learning: Training vs. Ranking
    230
  24. The Continuous Learning Machine: Designing a Loop That Actually Turns
    228
  25. The Next-Gen Low-Latency Standards: LL-HLS & MoQ
    203
  26. Designing a Data Curation System Around a Vector Database
    230
  27. Extracting Context from Live Video: The Architecture Got Simpler When We Stopped Building Features
    263
  28. The New Ad Stack Behind Live Sports Streaming: Inside SGAI, EABN, and the Standards Race to Fix Live Monetization
    674
  29. Designing MLOps Architectures to Handle Seasonal Data Drift in EV Fleet Models
    201
  30. From 15 to 40+ FPS: Accelerating PyTorch Object Detection on Automotive ECUs
    233