In this article, I will walk you through how the world wide web works at a fundamental level.

The core technology is HTTP - Hypertext Transfer Protocol. It's the communication protocol you use when you browse the web.

At a fundamental level, when you visit a website, your browser makes an HTTP request to a server. Then that server responds with a resource (an image, video, or the HTML of a web page) -  which your browser then displays for you.

This is HTTP's message-based model. Every HTTP interaction includes a request and a response.

By its nature, HTTP is stateless.

Stateless means that all requests are separate from each other. So each request from your browser must contain enough information on its own for the server to fulfill the request. That also means that each transaction of the message based model of HTTP is processed separately from the others.


The URL (Uniform Resource Locator) is probably the most known concept of the Web. It is also one of most important and useful concepts. A URL is a web address used to identify resources on the Web.

The idea of the web is structured around resources. From its beginnings the Web was the platform for sharing text/HTML files, documents, images etc, and as such it can be considered a collection of resources.

Example of an URL

Protocol — Most often they are HTTP (or HTTPS for a secure version of HTTP).

Other notable protocols are:

  • File Transfer Protocol (FTP) — is a standard protocol used for transferring files between a client and a server over a network.
  • Simple Mail Transfer Protocol (SMTP) is a standard for email transmission.

Domain — Name that is used to identify one or more IP addresses where the resource is located.

Path —Specifies the resource location on the server. It uses the same logic as a resource location used on the device where you are reading this article (i.e. /search/cars/VWBeetle.pdf or C:/my cars/VWBeetle.pdf).

Parameters — Additional data used to identify or filter the resource on the server.

Note: When searching for articles and more information about HTTP, you may encounter the term URI (or uniform resource identifier). URI is sometimes being used instead of URL but mostly in formal specifications and by people who want to show off. :)

HTTP Requests

In HTTP, every request must have an URL address. Additionally, the request needs a method. The four main HTTP methods are:

  • GET
  • PUT
  • POST

I will explain these methods, and more, in the HTTP Methods section of this article.

And these methods directly correspond to actions:

  • read
  • update
  • create
  • delete

All HTTP messages have one or more headers, followed by an optional message body. The body contains the data that will be sent with the request or the data received with the response.

The first part of every HTTP request holds three items:


  • GET /adds/search-result?item=vw+beetle HTTP/1.1

When a URL contains a “?” sign, it means it contains a query. That means it sends parameters of the requested resource.

  1. The first part is a method which tells which HTTP method is used. Most commonly used is the GET method. GET method retrieves a resource from the web server and since GET doesn’t have a message body nothing after the header is needed.
  2. The second part is a requested URL.
  3. The third part is a HTTP version being used. Version 1.1. is the most common version for most browsers, however, version 2.0 is taking over.

There are also some other interesting things in an HTTP request:

Referer header — tells the URL from where the request has originated.

User-Agent header — additional information about the browser being used to generate the request.

Host header — uniquely identifies a host name; it is necessary when multiple web pages are hosted on the same server.

Cookie header — submits additional parameters to the client.

HTTP Responses

Just like in HTTP requests, HTTP responses also consist of three items:


HTTP/1.1 200 OK

  1. The first part is the HTTP version being used.
  2. The second part is the numeric code of the result for the request.
  3. The third part is a textual description of the second part.

There are some other interesting things in an HTTP response:

Server header — information about which web server software is being used.

Set-Cookie header — issues the cookie to the browser.

Message body — it is common for an HTTP response to hold a message body.

Content-Length header — tells the size of the message body in bytes.

HTTP Methods

The most common methods are GET and POST. But there are a few others, too.

GET —  You use this method to request data from a specified resource where data is not modified it in any way. GET requests do not change the state of resource.

POST — You use this method to send data to a server to create a resource.

PUT — You use this method to update the existing resource on a server by using the content in the body of the request. Think of this as a way to "edit" something.

HEAD —  You use this method the same way you use GET, but with the distinction that the return of a HEAD method should not contain body in the response. But the return will contain same headers as if GET was used. You use the HEAD method to check whether the resource is present prior of making a GET request.

TRACE — You use this method for diagnostic purposes. The response will contain in its body the exact content of the request message.

OPTIONS — You use this method to describe the communication options (HTTP methods) that are available for the target resource.

PATCH —  You use this method to apply partial modifications to a resource.

DELETE —You use this method to delete the specified resource.


Representational state transfer (REST) is an architecture style where requests and responses contain representations of the current state of the systems resource.

“Regular” way:


You can learn more about REST here if you're curious.

HTTP Headers

There are three main components that make up the request/response structure. These include:

  • First line
  • Headers
  • Body/Content

We already talked about the first line in HTTP requests and responses, and body function was mentioned too. Now we'll talk about HTTP headers.

The HTTP headers are added after the first line and are defined as name:value pairs separated by a colon. HTTP headers are used to send additional parameters along with the request or response.

As I already said, the body of the message includes the data to be sent with the request or the data received along with the response.

There are different types of headers that are grouped based on their usage into 4 broad categories:

  • General header — Headers that can be used in both requests and response messages and that are independent of the data being exchanged.
  • Request header — These headers define parameters for the data requested or parameters that give important information about the client making the request.
  • Response header — These headers contain information about the incoming response.
  • Entity header — The entity headers describe the content that makes up the body of the message.
Types of headers

HTTP status codes

Browsing the web, you may have encountered "404 error: not found" pages or "500 errors: server is not responding" pages.

These are HTTP status codes.

Every HTTP response message must contain an HTTP status code in its first line, telling us the result of the request.


There are five groups of status codes which are grouped by the first digit:

  • 1xx — Informational.
  • 2xx — The request was successful.
  • 3xx — The client is redirected to a different resource.
  • 4xx — The request contains an error of some kind.
  • 5xx — The server encountered an error fulfilling the request.

Here's a full list of HTTP Status Response Codes and their explanation.

HTTPS (Hypertext Transfer Protocol Secure)

The secure version of HTTP protocol is HyperText Transfer Protocol Secure (HTTPS). HTTPS provides encrypted communication between a browser (client) and the website (server).

In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or Secure Sockets Layer (SSL).

The protocol is therefore also often called HTTP over TLS, or HTTP over SSL.

Both the TLS and SSL protocols use an asymmetric encryption system. Asymmetric encryption systems use a public key (encryption key) and a private key (decryption keys) to encrypt a message.

Anyone can use the public key to encrypt a message. However, private keys are secret, and that means that only the intended receiver can decrypt the message.

Example of asymmetric encryption system

SSL/TLS handshake

When you request a HTTPS connection to a website, the website sends its SSL certificate to your browser. That process where your browser and website initiate communication is called the “SSL/TLS handshake.”

The SSL/TLS handshake involves a series of steps where browser and website validate each other and start communication through the SSL/TLS tunnel.

As you probably noticed, when a trusted secure tunnel is used during in a HTTPS connection, the green padlock icon is displayed in the browsers address bar.

Example of one of my secure pages

Benefits of HTTPS

The major benefits of a HTTPS are:

  • Customer information, like credit card numbers and other sensitive information, is encrypted and cannot be intercepted.
  • Visitors can verify you are a registered business and that you own the domain.
  • Customers know they are not suppose to visit sites without HTTPS, and therefore, they are more likely to trust and complete purchases from sites that use HTTPS.

Thank you for reading! Check out more articles like this on my freeCodeCamp profile. And check out other fun stuff I build on my GitHub page.