Simple Web Server

Introduction to Modern Application Development

Overview of the Course

• The course focuses on modern application development, introducing practical examples and code snippets.

• A simple web server example is presented, written in shell script, demonstrating basic command execution in Linux/Unix.

Understanding Shell Script Components

• The while true; do loop indicates an indefinite repetition of commands until manually stopped.

• The pipe symbol (|) signifies a two-stage process where output from one command is used as input for another.

Importance of Familiarity with Unix/Linux

Benefits of Learning Scripting

• Gaining familiarity with Unix/Linux scripting enhances understanding of underlying processes in web app development.

• While the course will cover necessary concepts, additional research may be required for clarity on certain topics.

Detailed Breakdown of the Web Server Code

Echo Command Functionality

• The echo -e command outputs text to standard output (STD out), which can be redirected using pipes.

• The server responds with HTTP/1.1 status code 200 OK, indicating successful requests.

HTTP Status Codes Explained

• HTTP defines various status codes:

• 200: OK (successful request)

• 301: Moved Permanently

• 404: Not Found (common error message).

Server Implementation Using Netcat

How Netcat Functions

• The echo command outputs the current date and time, which is piped into the netcat (nc) command.

• Netcat listens on localhost at port number 1500, responding to incoming requests without interpreting them.

Practical Demonstration of Server Creation

• A simple web server can be created using a single line of shell script code that combines all components discussed.

• The shebang (#!/bin/bash) at the top specifies which interpreter should execute the script.

Understanding Shell Interaction and HTTP Requests

Introduction to Shell and Script Functionality

• A shell is a tool for interacting with Unix-based systems, with bash being the specific shell used in this context.

• The script in question runs an infinite while loop, waiting for input but initially appears inactive due to its simplistic design.

Testing Server Functionality

• To verify the script's operation as a web server, another shell is opened to connect using the curl command.

• Curl is highlighted as a powerful tool for app development that simplifies sending custom requests to web servers without needing deep knowledge of HTTP protocols.

Crafting HTTP Requests

• An HTTP request format is explained, emphasizing the structure of URLs which separate protocol from server details.

• The connection is established on localhost at port 1500, deviating from standard HTTP ports.

Expected Responses from the Server

• Anticipated output includes header information and date; however, curl primarily displays only the response body.

• When executing a request via curl, it generates a GET request indicating communication with the specified host and user agent details.

Analyzing Request Details

• The verbose flag (-v) in curl provides additional insights into the request-response cycle between client and server.

• The server listens on port 1500, processing incoming requests dynamically by executing commands like echoing data along with timestamps.

MIME Types and Request Structure

• MIME (Multimedia Internet Mail Extensions), originally designed for email attachments, plays a crucial role in defining content types exchanged over web protocols.

• A typical HTTP request consists of mandatory components (like GET method), while some headers are optional yet beneficial for proper responses based on client type.

Conclusion on Client Behavior

• User agents inform servers about client capabilities; different browsers may elicit varied responses based on their identification.

Understanding HTTP Requests and Responses

Analyzing the Curl Command Response

• The curl command curl -v http://localhost:1500 is executed to analyze the response from a web server, providing insight into the communication protocol between client and server.

• Debug information from curl, indicated by lines starting with an asterisk, is not part of the actual protocol; it serves only for debugging purposes.

• The address ::1 represents an IPv6 format indicating localhost (the local machine), which can be ignored for basic understanding at this stage.

TCP Connection Details

• A successful connection to localhost on port 1500 indicates that a server is running; otherwise, error messages would appear.

• The last part of the curl output signifies that no further information was received after establishing the connection.

Structure of HTTP Request

• The request sent by curl includes GET / HTTP/1.1, where "GET" specifies the type of request for information from the server.

• The "/" in the request denotes a request for root-level information without additional details.

Versions of HTTP Protocol

• Various versions exist, with HTTP/1.1 being predominant today; earlier versions like HTTP/1.0 are rarely used now.

• Newer protocols such as HTTP/2.0 and upcoming HTTP/3 aim to enhance performance but are not yet universally adopted.

Server Response Overview

• Upon receiving a request, the server responds with HTTP/1.1 200 OK, confirming successful processing of the request based on hardcoded responses in its script.