Slide 2: Introduction to the Internet (Expanded Version)

The Internet began in the 1960s as part of a U.S. Department of Defense (DoD)
initiative. The goal was to create a large-scale computer network to aid researchers
working on defense-related projects. This network would facilitate communication,
program sharing, and remote computer access. The project was led by the Advanced
Research Projects Agency (ARPA), which funded various research institutions to
develop the system. The result was ARPANET, the first operational packet-switching
network, which would lay the groundwork for the modern Internet. ARPANET
revolutionized the way information is shared and accessed worldwide, moving from
academic and military use to a broader, global communication system.

Slide 3: BITnet & CSnet (Late 1970s - Early 1980s)

BITnet (Because It's Time Network): Launched in the late 1970s, BITnet focused on
email and file transfer services between universities and academic institutions. It
enabled efficient communication and collaboration between researchers, helping
expand the reach of digital communication in academia.

CSnet (Computer Science Network): Introduced in the early 1980s, CSnet was
designed for institutions without access to ARPANET. It offered a broader network
for computer science researchers at universities, allowing them to share resources
and collaborate on projects.

These networks, BITnet and CSnet, were pivotal in expanding the scope of
networking beyond military and government applications to academia and research
institutions.
NSFnet (1986)
In 1986, the National Science Foundation (NSF) created NSFnet to support civilian,
non-DoD-funded research. Initially connecting five supercomputing centers, NSFnet
enabled researchers across the United States to share data and computational
resources. It played a key role in the evolution of networking, bridging the gap
between military and civilian use. NSFnet helped build the infrastructure that would
form the backbone of the modern Internet.
By 1990
By 1990, NSFnet had grown significantly, surpassing ARPANET in size and scope. It
became the main network backbone for academic and research purposes,
connecting universities, research institutions, and eventually other organizations.
The widespread growth of NSFnet facilitated the commercialization of the Internet
and the transition toward public access, setting the stage for the global network we
know today.

Slide 4: What the Internet Is

The Internet is a vast, interconnected network of computer systems that spans the
globe. It serves as the backbone for modern communication, allowing for the
exchange of information across diverse sectors, including private, public, academic,
business, and government networks. The Internet has fundamentally transformed
how we share knowledge, interact with others, and conduct business.
Unified by TCP/IP (Since 1982)
At the heart of the Internet is the Transmission Control Protocol/Internet Protocol
(TCP/IP), a set of standardized communication rules that enable devices to exchange
data over the network. TCP/IP is crucial because it ensures that different types of
devices, regardless of their underlying hardware or software, can communicate
seamlessly with each other.

TCP: The Transmission Control Protocol breaks data into small chunks called packets
and ensures that these packets arrive intact at their destination. It also ensures data
is delivered in the correct order and handles retransmission if packets are lost during
transmission.

IP: The Internet Protocol takes care of addressing and routing these packets to their
correct destinations. Each device connected to the Internet has a unique address (IP
address), allowing packets to be sent to the right location. Without IP, packets
wouldn’t know where to go, making it impossible for devices to communicate with
each other.

Together, TCP/IP allows different devices, regardless of manufacturer or operating

system, to exchange data with each other reliably and efficiently.
Seamless Integration of Devices
One of the Internet's major strengths is its ability to seamlessly integrate diverse
devices. Whether you're using a desktop computer, a smartphone, a server, or a
smart home device, all these devices communicate using the same underlying TCP/IP
protocols. This standardization hides the technical differences between devices and
allows them to work together on the same network, even if they come from
different manufacturers or use different operating systems. This is crucial because it
means that no matter the device or software platform, as long as it supports TCP/IP,
it can connect to the Internet and interact with other devices.
Conclusion: The Foundation of Global Communication
By unifying a wide range of systems under a single protocol (TCP/IP), the Internet has
become the foundation for global communication, commerce, and innovation. It
enables people to connect, share information, collaborate, and do business across
borders, and it continues to evolve as more devices and services come online. The
flexibility and scalability of the Internet ensure that it will remain at the center of
technological advancement for years to come.

Slide 5: Internet Protocol Addresses (IP Addresses)

An IP address is a unique numeric identifier assigned to every device (or "node")
connected to the Internet. It ensures that data sent across the network reaches the
correct destination, functioning like a home address that tells data packets where to
go.
Structure of an IP Address
An IP address is typically a 32-bit binary number, but it's often represented in a
human-readable format known as dotted decimal notation. For example, the
address [Link] is an IP address written in dotted decimal format.
The address is divided into four octets (groups of 8 bits), each ranging from 0 to 255.
This gives us four numbers, each between 0 and 255, separated by periods (dots).
Example:
[Link]
192 is the first octet (0-255)
168 is the second octet (0-255)
1 is the third octet (0-255)
1 is the fourth octet (0-255)
This 32-bit format allows for about 4.3 billion unique addresses (2^32).

Large organizations or government departments (e.g., the Department of Defense)

may be assigned large blocks of IP addresses.
Example: The block [Link] to [Link] provides over 16 million unique IP
addresses.

Smaller organizations may be assigned smaller blocks of IP addresses.

Example: A block like [Link] to [Link] gives an organization 256 IP
addresses.

Purpose of IP Addresses
Unique Identification: Every device connected to the Internet must have a unique IP
address to send and receive data. Without a unique identifier, the system wouldn’t
know where to send data or where it came from.

Routing: IP addresses are also critical for routing data packets across the Internet.
When a user sends a message, the data is broken into small packets, each of which is
routed individually through different paths across the network. Each packet is
directed to its destination using the destination IP address, ensuring it reaches the
right place.
This routing system allows data to traverse the vast network of interconnected
devices and reach its intended destination, whether it’s a computer in your home, a
server in a data center, or an IoT device.
Conclusion: Seamless Operation of the Internet
IP addresses provide the foundation for communication on the Internet. They ensure
that data can travel across the global network, directing packets to the correct
destination, whether it's a single device or a large organizational network. By
managing and assigning these unique identifiers, the Internet can continue to grow
and allow diverse systems to communicate without conflict.

Slide 6: Domain Names

To make the Internet more user-friendly, we use domain names instead of requiring
users to remember numeric IP addresses. Domain names are text-based labels
assigned to devices, services, or websites, simplifying the process of accessing
resources on the Internet.
Structure of Domain Names
A domain name consists of several parts, ordered from the most specific to the most
general:

Host Name: This is the name of the specific device or service. For example, in the
domain name [Link], movies is the host name.

Domains: Domains are collections of machines or resources. In the example,

marxbros, comedy, and com represent progressively larger domains, with com being
the largest or most general. The first domain is the smallest, and the last domain is
the largest.

Example:
[Link]
movies = Host name (specific device or service)
marxbros, comedy, com = Domains (larger groups)
com = Top-Level Domain (TLD)
Last Domain (Top-Level Domain - TLD)
The Top-Level Domain (TLD) specifies the type of organization or the geographical
region associated with the domain. Common TLDs include:
.com for commercial organizations
.edu for educational institutions
.org for non-profit organizations
Country code TLDs like .uk (United Kingdom), .in (India), etc.
Fully Qualified Domain Name (FQDN)
A Fully Qualified Domain Name (FQDN) includes the entire address of a device or
service, starting with the host name and including all associated domains. An FQDN
is the complete web address that a user types into the browser to reach a website or
service.
Example:
[Link]
This is an FQDN because it includes the full hierarchy of domain names, starting from
the host to the top-level domain.
DNS (Domain Name System)
The Domain Name System (DNS) is responsible for translating domain names (like
[Link]) into their corresponding IP addresses (like
[Link]). This translation process enables devices to locate each other on the
Internet.
DNS servers manage this process, acting like a "directory" for the Internet.
This system ensures that users can access websites using simple, human-readable
names while computers communicate using numerical IP addresses.
Domain names simplify navigation and make the Internet more accessible, while
DNS ensures that everything works behind the scenes efficiently.
Slide 7: Domain Name Conversion: DNS to IP Address
Since computers use IP addresses (numbers) to communicate, but humans prefer
domain names (text), a process is needed to convert domain names into IP
addresses. This process is handled by the Domain Name System (DNS).
Steps in DNS to IP Conversion:

User Inputs Domain Name:

A user enters a domain name (e.g., [Link]) into their web browser.

Contacting the Name Server:

The browser sends the domain name request to a DNS resolver or name server. The
name server’s job is to find the corresponding IP address for that domain name.

Returning the IP Address:

Once the DNS server locates the correct IP address, it sends this address back to the
user's device.

Accessing the Destination:

Using the IP address, the browser establishes a connection to the server hosting the
website and loads the requested page.
Why Conversion is Necessary:
Computers only understand numbers (IP addresses), not textual domain names.
The DNS system ensures that users can interact with websites using user-friendly
domain names (e.g., [Link]), while computers use numerical IP
addresses behind the scenes to connect devices.
In summary, DNS acts as a crucial intermediary, enabling the user-friendly browsing
experience while ensuring that devices can communicate with each other efficiently
through numerical IP addresses.
Slide 8: Role of the Name Server in Domain Name Conversion
A name server plays a critical role in translating domain names into IP addresses,
which allows users to access the corresponding host machine.
Responsibility of the Name Server
The name server's primary responsibility is to map a human-readable domain name
(like [Link]) to its corresponding IP address. This allows the network to
route the user's request to the correct location.
Recursive Query Process
If a name server doesn't know the IP address for a domain name, it follows a
recursive query process to find the correct address. This process involves querying
different types of servers in a hierarchical structure:
Root DNS Server: The first server in the chain, which knows where to find
information about top-level domains (TLDs).
TLD Server: For example, for .com, the TLD server will help find the authoritative
name server for [Link].
Authoritative Server: This is the final server in the query, holding the authoritative IP
address for the specific domain.
The process continues until the correct IP address is found.
Conclusion
This system ensures accurate routing of data across the Internet while providing a
user-friendly experience for navigating websites. The name server acts as a crucial
intermediary in converting domain names into IP addresses, making the Internet
accessible to all users.

Slide 9: Basic Architecture of Domain Name Resolution

The process of how a domain name connects to a web server to deliver web content
can be broken into key components:
Key Components
Domain Name: Represents the URL (e.g., [Link]) that a user types into their
browser to access a website.
Client System: The user’s device (e.g., computer, smartphone) that makes the
request to access the website.
Internet: The global network of computers and servers that routes data between the
client system and the web server.
Name Server: Translates the domain name into an IP address, which the web server
uses to identify itself on the Internet.
IP Server (Web Server): The actual server that hosts the website’s content and
responds to requests from the client system.
Process
The client system sends a request to the domain name (e.g., typing
[Link] in the browser).
The name server translates the domain into the correct IP address of the web server.
The web server sends the requested content back through the Internet to the client
system for display.
This process demonstrates how domain names and web servers work together to
deliver websites to users efficiently.

Slide 10: The World Wide Web (WWW)

The World Wide Web (WWW) was created in 1989 by Tim Berners-Lee, a researcher
at CERN (European Organization for Nuclear Research). It was initially designed to
facilitate information sharing among scientists globally, enabling them to access and
exchange research documents easily.
Key Components Developed
Hypertext Transfer Protocol (HTTP): A protocol for transferring hypertext documents
(web pages).
HTML (Hypertext Markup Language): The language used to structure and format
documents on the web.
URLs (Uniform Resource Locators): A system for naming and accessing resources on
the web.
The introduction of hyperlinks allowed users to navigate between documents and
websites, making information sharing and collaboration more accessible and user-
friendly. This development revolutionized how information is accessed and
contributed to the growth of the Internet.
Slide 11: Hypertext
Hypertext refers to a way of organizing and presenting text so users can quickly
navigate between different pieces of information using hyperlinks. These links are
embedded in the text and can lead to other documents, websites, or even sections
within the same document.
Example
When reading an article online, certain words or phrases may be highlighted or
underlined. By clicking these links, users are taken to related pages or additional
information. This enables a non-linear flow of information, where users can jump
between topics or references.
Role in the World Wide Web
In the context of the Web, hypertext allows users to easily browse through
interconnected web pages, enhancing their ability to explore vast amounts of
information. Hypertext was a revolutionary feature of the Web, making the Internet
more interactive and user-driven.

Slide 12: Pre-Web Development of Hypertext and Internet vs. Web(Imp)

Development of Hypertext Before the Web
Before the World Wide Web, technologies like Xerox's NoteCards and Apple's
HyperCard were among the early systems that allowed users to create interactive
documents with hyperlinks. These tools contributed to the development of
hypertext systems that influenced the creation of the Web.
Internet vs. Web
The Internet: The physical and technical infrastructure of the global network,
consisting of interconnected computers, devices, and communication protocols (like
TCP/IP) that enable data exchange.
The Web: A service that operates on top of the Internet, consisting of software,
protocols, and documents that allow users to access and share information. It uses
protocols like HTTP and HTML to manage the formatting and transfer of documents.
Summary
The Internet: The underlying infrastructure (the global network of devices).
The Web: A collection of tools and protocols (such as HTTP and HTML) that allow
users to interact with content hosted on the Internet.

Slide 13: Client-Server Communication & Web Browsers(important)

Client-Server Communication
Client: The device that requests information (e.g., when you type a web address or
click a link).
Server: The device that provides information, like a web server that hosts websites
and sends content to the client.
What Web Browsers Do
A web browser (e.g., Chrome, Firefox, Safari) acts as a client on your device. When
you type a URL or click on a link, the browser sends a request to the server for the
web page. The server sends back the page content, which the browser displays to
you.
Why It’s Called a Browser
The term browser refers to the idea of browsing or exploring information. Just like
browsing a catalog or book, a browser lets users navigate through web content,
search, and interact with websites.
Web browsers are essential tools for exploring the web and viewing the content
stored on web servers, making the Internet accessible and interactive.

Slide 14: Early Web Browsers, HTTP, and Requests for Program Execution
(Important)
Early Text-Based Browsers
The first web browsers were simple and text-only, without any graphical capabilities.
These browsers displayed only text-based documents, and users interacted with
them via keyboard commands rather than a graphical interface.
Mosaic - The First GUI Browser
Released in 1993 by the National Center for Supercomputing Applications (NCSA),
Mosaic revolutionized web browsing by introducing a Graphical User Interface (GUI).
Key Features of Mosaic:
GUI allowed users to click on images, links, and buttons instead of typing commands.
Mosaic supported the display of images, videos, and other multimedia alongside text,
making web browsing much more visually appealing.
It was available on multiple platforms, including UNIX, Macintosh, and Windows,
which broadened its reach.
Mosaic's innovations made the web accessible and engaging to a wider audience,
significantly contributing to the web's rapid growth.
HyperText Transfer Protocol (HTTP)
HTTP is the protocol that facilitates communication between web browsers (clients)
and web servers.
Client-Server Model: When you type a web address or click on a link, your browser
sends an HTTP request to the server, asking for a specific document. The server
responds by sending the requested document back to the browser.
Example: When you visit a website, your browser uses HTTP to fetch and display the
website’s content, including HTML, images, and other resources.
Requests for Program Execution
Some HTTP requests require servers to execute programs, such as processing search
queries or performing calculations.
Client Request: A browser sends a request for the server to run a specific program.
For example, a search query on Google.
Program Execution: The server processes the request (e.g., searching its database).
Server Response: The results are returned to the client, often as a dynamically
generated web page.
This client-server interaction forms the backbone of modern web applications.

Slide 15: Web Servers: Key Concepts and Operations (Important)

Web servers are fundamental components of the Internet, responsible for delivering
content such as web pages, images, and videos to users when they request it
through web browsers.
Web Servers: Key Points

Definition and Role:

Web servers store and deliver web content to browsers (clients).
They respond to requests by processing the request and sending the requested
content to the client.

Slave Programs:
Web servers are referred to as "slave programs" because they do not initiate actions
on their own.
They only respond when a client (browser) sends a request, like typing a URL or
clicking a link.

Common Web Servers:

Apache: Open-source and free, Apache is one of the most widely used web servers,
supporting Linux, Windows, and macOS.
IIS (Internet Information Services): Developed by Microsoft, IIS is used on Windows
servers and commonly found in enterprise environments.
Conclusion:
Web servers deliver requested content (static or dynamic) to clients, playing a critical
role in Internet communication. Apache is popular in open-source setups, while IIS
dominates Windows-based environments.

Slide 17: Web Server Operation (Important)

Web servers are crucial for delivering content to users, and their operation is central
to how the internet functions. Here’s how they interact with web browsers:

Initiating Communication (URL Request):

When a user enters a URL (Uniform Resource Locator) into the browser, it specifies
the address of the resource (e.g., a webpage or image) on the web server.
A URL includes:
Protocol (e.g., http:// or [Link]
Server Address (e.g., [Link])
Path to the resource (e.g., /[Link])
The browser sends this URL request to the web server, which retrieves the specified
file or resource.
Requesting Documents or Programs:
The URL can request:
Data files: Static files like HTML documents, images, or videos stored on the server.
Programs: Dynamic content, like a script or program (e.g., PHP or Python), which the
server executes and returns the generated output (e.g., search results, user profile).

Running in the Background:

Web servers operate as background processes in the operating system, meaning
they are always running, awaiting HTTP requests from browsers.
They don’t require direct user interaction but constantly monitor incoming requests
and process them when received.

Handling HTTP Commands / Handling Events:

Web servers listen for incoming HTTP requests through specific network ports:
Port 80 for HTTP (unencrypted).
Port 443 for HTTPS (encrypted).
When a request is received, the server performs the required operation:
Serve static files (e.g., HTML or images).
Execute programs (e.g., scripts or database queries).
The server processes the request and sends the appropriate response (document,
image, or dynamic content) back to the browser.

Slide 18: HTTP Commands and URL Translation (optional)

HTTP Requests and URLs:
Every HTTP request from a browser includes a URL that specifies the location of the
requested resource.
Structure of a URL:
Protocol (e.g., http:// or [Link]
Host Server (e.g., [Link])
File/Program Path (e.g., /[Link] or /[Link])
Translation of URL by Web Server:
When a web server receives an HTTP request, it translates the URL into an actual
resource it can serve. This process leads to two main outcomes:
a) File Name:
If the URL refers to a static resource (e.g., HTML, image, or CSS file), the server looks
for the corresponding file in its directories and sends it back to the browser.
Example: For the URL [Link] the server returns the
[Link] file from its storage.
b) Program Name:
If the URL refers to a program or dynamic content generator (e.g., a PHP or Python
script), the server executes the program.
Example: For the URL [Link] the server
executes the [Link] script, processes the query=cat parameter, and returns the
generated result (e.g., search results) to the browser.

Returning the Response:

If the URL points to a static file, the server sends the file contents (e.g., HTML,
images, or CSS) directly to the browser.
If the URL points to a program, the server processes the program and sends back the
dynamic output (e.g., generated HTML, search results, or processed data).

Slide 19-22: Uniform Resource Locators (URLs) (Important)

A Uniform Resource Locator (URL) is a reference or address used to identify and
locate resources on the internet, such as documents, images, or programs. URLs
provide a standardized method to access these resources over a network. They
typically consist of two main components: the scheme and the object-address.
General Structure of a URL:
The general format of a URL is:
scheme:object-address
It consists of the following key parts:
Scheme:
Definition: The scheme specifies the protocol or method used to access the resource.
It indicates how the resource should be retrieved from the network.
Common Schemes:
http: HyperText Transfer Protocol (most common for web browsing).
https: Secure HTTP (for secure communication over the web).
ftp: File Transfer Protocol (for transferring files).
mailto: Used to initiate email communication.
Examples:
http:// (standard web browsing protocol)
ftp:// (file transfer)
mailto: (used for email addresses)

Object-Address:
Definition: The object-address part specifies the location of the resource on the
internet, usually divided into two sub-parts:
Domain Name: The fully qualified domain name (FQDN) or host, which identifies the
server that stores the resource.
Path to the Document: Specifies the exact file or directory on the server.

Examples of URL Structure:

[Link]
ftp: The scheme (FTP protocol for file transfer).
[Link]: The domain name of the server hosting the resource.
/file/path/[Link]: The path to the specific file on the server.
HTTP Protocol Example:
[Link]
http: The scheme (HTTP protocol).
[Link]: The domain name (server location).
/[Link]: The path to the document (webpage in this case).
In Summary:
A URL specifies how to access a resource on the internet (via a scheme) and where
the resource is located (through a domain name and path).
Common schemes include [Link] [Link] [Link] and [Link]
The domain name points to the server, while the path indicates the specific resource
or file on that server.

Slide 22: Multipurpose Internet Mail Extensions (MIME) (Important)

MIME (Multipurpose Internet Mail Extensions) is a standard that was initially
developed to enable the exchange of different types of content, such as text, images,
videos, and audio, in email messages. Over time, MIME has been adapted to work
with web browsers and other Internet protocols to define how files should be
handled, helping to manage diverse content types across the web.

MIME and Its Use in Web Browsers:

Purpose: MIME allows web servers to inform web browsers about the type of
content being sent. This enables browsers to understand how to process and display
the content correctly.
MIME Type: The MIME type is included in the HTTP response header sent by the
server. This helps the browser understand whether it should display text, render an
HTML page, or play a video, for example.
MIME Type Structure: A MIME type is typically structured as:
type/subtype
Type: The primary classification of the content (e.g., text, image, audio, video).
Subtype: The specific format of the content within that type (e.g., html, plain, gif,
jpeg).

Common MIME Type Examples:

Text Types:
text/plain: Plain text (no formatting).
text/html: HTML document (web page content).
Image Types:
image/gif: GIF image (Graphics Interchange Format).
image/jpeg: JPEG image (Joint Photographic Experts Group).
Audio and Video Types:
audio/mpeg: MP3 audio format.
video/mpeg: MPEG video format.
video/quicktime: QuickTime video format (used by Apple devices and applications).
Example MIME Types:
Text-based files:
text/plain: Simple text file (no formatting).
text/html: Web page with HTML code.
Image files:
image/png: Portable Network Graphics image format.
image/jpg or image/jpeg: JPEG image format.
Video files:
video/mpeg: MPEG video format.
video/quicktime: QuickTime video format.

Why MIME is Important:

In Web Browsers: MIME allows browsers to determine how to display or process
content. For example, text/html will be rendered as a webpage, while image/jpeg
will be displayed as an image.
In Email: MIME is used to handle attachments like images, audio files, and
documents. The MIME type specifies the file type, so the email client can either
display it or prompt the user to download it.
Slide 23: MIME and File Handling When a server sends a document to a browser, it
specifies the MIME type to inform the browser about how to handle the file. This can
be done in two main ways:

File Name Suffix (Implicit Type Identification):

The file extension (e.g., .html, .jpg, .mp3) can often indicate the MIME type
automatically. Common examples include:
.html → text/html
.jpg or .jpeg → image/jpeg
.mp3 → audio/mpeg
Examples:
[Link] → text/html
[Link] → image/jpeg
audio.mp3 → audio/mpeg

Explicit MIME Type from Server:(optional)

Servers can explicitly define the MIME type in the HTTP response header using the
Content-Type field. This allows the server to override the file extension-based type
determination.

Examples:
Content-Type: text/html → The browser knows to render it as HTML.
Content-Type: image/jpeg → The browser knows to display the image.
Content-Type: application/pdf → The browser knows to either display or prompt the
user to download a PDF file.

slide no 24
HyperText Transfer Protocol (HTTP) (Important)
HTTP (HyperText Transfer Protocol) is the core protocol that enables communication
on the web. It governs how data is exchanged between clients (typically web
browsers) and servers. HTTP defines how messages are formatted and transmitted,
ensuring that both the browser (client) and the server understand and respond
appropriately to requests.
HTTP operates in two primary phases: Request Phase and Response Phase.
Request Phase: In the request phase, the client (usually a web browser) sends a
request to the server for a specific resource, such as a webpage or file. The request is
structured with several key components:
a) Request Line: This is the first line of the HTTP request, which consists of:
HTTP Method: The action the client wants to perform (e.g., GET, POST, PUT, DELETE).
URL Path: The specific resource the client is requesting (e.g., /[Link]).
HTTP Version: The version of the HTTP protocol being used (e.g., HTTP/1.1, HTTP/2).
Example:
GET /[Link] HTTP/1.1
GET: The method, asking the server to send the resource.
/[Link]: The resource (a webpage) being requested.
HTTP/1.1: The version of HTTP being used for this request.
b) Header Fields: After the request line, the client sends additional information in
the form of headers. These headers provide more details about the request, such as:
Host: Specifies the domain name of the server (e.g., Host: [Link]).
User-Agent: Identifies the client (browser type, operating system).
Accept: Specifies the types of content the client can handle (e.g., Accept: text/html,
application/json).
Example:
Host: [Link]
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36
Accept: text/html
c) Blank Line: A blank line separates the headers from the body of the request.
d) Message Body (Optional): For some HTTP methods, such as POST or PUT, a
message body is included. This body contains the data being sent to the server (e.g.,
form data, uploaded files).
Response Phase:
In the response phase, the server processes the client's request and sends back a
response. The response typically consists of the following components:
a) Status Line:
HTTP Version: The version of HTTP used by the server to respond (e.g., HTTP/1.1).
Status Code: A 3-digit code indicating the result of the request (e.g., 200 for success,
404 for "Not Found").
Status Message: A brief message describing the status code (e.g., OK for a successful
request).
Example:
HTTP/1.1 200 OK
b) Header Fields: Similar to the request phase, the response includes header fields
that provide additional information about the response, such as:
Content-Type: Specifies the type of content being returned (e.g., text/html,
application/json).
Content-Length: Indicates the size of the response body.
c) Message Body: The actual data the server is returning to the client. This could be
an HTML document, an image, a JSON response, or any other type of content.
Example Response:
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 1234

<html>
<head><title>Degrees</title></head>
<body><h1>Welcome to the Degrees Page!</h1></body>
</html>

Example of an HTTP Request: Here’s an example of a basic HTTP GET request for a
webpage: GET /[Link] HTTP/1.1 Host: [Link] User-Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/91.0.4472.124 Safari/537.36 Accept: text/html
GET: The method requesting data.
/[Link]: The resource (webpage) being requested.
Host: Specifies the domain of the server ([Link]).
User-Agent: Identifies the browser making the request.
Accept: Specifies that the client can handle HTML responses.
Common HTTP Methods:

GET:
Requests data from the server (e.g., to retrieve a webpage or file).
Typically used for fetching resources like HTML pages, images, etc.
POST:
Sends data to the server (often used to submit form data or upload files).
The data is included in the body of the request.

PUT:
Replaces data on the server with the data provided in the request body.
Used for updating existing resources.

DELETE:
Deletes a specified resource from the server.
Typically used to remove a file or record.

In Summary:
HTTP is the protocol that enables communication between clients and servers on the
web.
It operates in two phases: Request Phase (where the client sends a request to the
server) and Response Phase (where the server sends a response back to the client).
HTTP methods define the actions clients want to perform: GET (retrieve data), POST
(send data), PUT (update data), and DELETE (remove data).