HTTP and Cricket: A Fun Take on Internet Basics

What is HTTP and Why Cricket?

Most of us play (or) watch cricket and enjoy watching it and we know the rules of game that’s what it makes interesting to watch, but why am I talking about cricket when this article is about how the internet works? Because using cricket as an analogy will help us better understand the internet!

If you open browser and type techcinefun.blogspot.com and enter, boom it will open the website and allow you to read, surf, play video (or) whatever you want to do.

How does this work behind the scenes? It relies on a standard set of instructions called HTTP or HTTPS.

Let’s bring cricket into the picture. To start a match, say between India and Pakistan, the first step is the toss. Without it, you can’t decide who will bat or bowl. Once the toss is done, the batting team sends two players to bat—not all 11 at once—while one player bowls from the other side. These step-by-step instructions to start and play the match are what we call a PROTOCOL in the web world.

Next, when the batsman at the striker’s end wants to rotate the strike, he transfers it to the non-striker. Similarly, in the web, HYPERTEXT allows you to transfer from one document or webpage to another using links. Just like a new batsman comes in when one gets out, hypertext lets you move seamlessly between connected pages.

So, there is there is some text with links (HYPER TEXT) which needs to transferred (TRANSFER) using some set of standard instruction (PROTOCOL), this is your HTTP

HTTP is Stateless PROTOCOL

Now what is state less, it is tech term (or) Jargon used in Internet.

Before understanding State less what is this Jargon, let’s go head to cricket to understand that, when a bowler bowls six legal deliveries it is called over, in cricket, we use specific terms to describe things, like calling six legal deliveries an 'over.' Similarly, in tech, 'stateless' is jargon that describes a process that doesn’t remember previous interactions.

For example, when a batsman faces a new ball, it doesn’t matter if he hit a four or six on the last delivery—he has to approach the new ball afresh. In the same way, HTTP doesn’t store any information about previous interactions. Every time you visit a webpage, you are treated as a new user, just like a batsman facing a fresh delivery.

Session

In cricket, a session refers to a specific period of play, such as a morning or evening session in Test matches. Players continue their performance across sessions, but once the session ends, they take a break and start fresh afterward.

Similarly, in the web world, a SESSION is a way to maintain a user's interaction with a website. For example, when you log in to a site, a session is created to track your activity during that visit. Once the session ends (you log out or close the browser), the connection is reset, just like players resuming after a lunch break with a clean slate.

Cookies

Imagine a cricket match being broadcast live. If you tune in mid-match, the commentator updates you about the score, wickets, and match situation. This helps you understand what’s happening without watching the entire game.

On the internet, COOKIES are like these updates (Key value pair). They store small pieces of information about your activity on a website, like login details or preferences, so you don’t need to start over every time you visit the same site. For instance, cookies can remember that you’re rooting for India in a cricket fantasy league.

HTTP Headers

Think about the cricket scoreboard. It doesn’t just show runs; it also displays information like overs, wickets, run rate, and more. These extra details make the game easier to follow.

In HTTP, HEADERS are like that scoreboard—they carry additional information about a request or response, such as the browser type, content type, or server details, helping ensure smooth communication between your device and the server.

Request-Response Model

Picture this: the captain tells the bowler to bowl a specific line and length. The bowler delivers the ball, and the captain observes the result. If it works, the captain continues with the same plan; if not, they adjust.

This is similar to the Request-Response Model in HTTP. Your browser sends a request (like asking for a webpage), and the server responds with the data you need (the webpage). If the response is unsatisfactory (like an error), adjustments (like retrying or fixing the URL) are made.

Types of Requests (GET, POST, DELETE)

• GET: Imagine asking the umpire for the match score—you’re simply requesting information.

• POST: When a batsman hits the ball, he’s adding runs to the scoreboard.

• DELETE: When a wicket falls, the batsman’s score is removed from the scoreboard.

In the web world, these are equivalent to requesting data (GET), submitting new data (POST), or deleting data (DELETE).

Different Versions of HTTP (1.1, 2)

Consider Test matches and T20s—both are cricket, but the pace and style differ significantly. Test matches are slower and allow more time for decision-making, while T20s are faster, with quick results.

Similarly, HTTP 1.1 was the older version, handling one request at a time. HTTP 2 introduced multiplexing, allowing multiple requests simultaneously, making the internet experience faster and more efficient—like the transition from Test cricket to T20s.

What is HTTPS?

Think of a cricket match with tight security—police ensure no disturbances, and players can focus on the game.

HTTPS (Hypertext Transfer Protocol Secure) is like this added security. It encrypts data transferred between your browser and the server, ensuring no one can intercept sensitive information, like passwords or credit card numbers.

User Agent

In cricket, a player’s kit—bat, gloves, helmet—represents their unique style and approach.

In the web world, the User Agent is your browser’s unique identity. It tells the server what type of device or browser you’re using, so the server can tailor its response accordingly, just like adjusting your game strategy based on the opponent.

TCP (Transmission Control Protocol)

Think of the partnership between two batsmen. They coordinate each run perfectly to avoid getting run out. Miscommunication leads to chaos.

Similarly, TCP ensures reliable communication between your device and the server, breaking data into packets and reassembling them in the correct order—just like a successful batting partnership.

FTP (File Transfer Protocol)

Imagine the ground staff delivering cricket equipment to the players. This exchange ensures the match can proceed smoothly.

On the internet, FTP is used to transfer files between systems. Whether uploading a blog or downloading match highlights, FTP is like the ground staff working behind the scenes.

IP (Internet Protocol)

Every cricket stadium has an address, helping teams and fans find their way there.

On the web, an IP address is like that stadium address. It identifies the location of a device on the internet, allowing data to find its way to the correct destination.

URL (Uniform Resource Locator)

Think of a ticket to a cricket match. It specifies the venue, match details, and seating arrangement.

A URL does the same for the web—it’s the unique address for a specific webpage or resource, telling your browser where to go.

DNS (Domain Name System)

Imagine remembering every player’s stats by their ID number instead of their name. Confusing, right?

The DNS is like a commentator, translating domain names (like techcinefun.blogspot.com) into IP addresses so that your browser knows where to find the website.

Cache

Picture a fielder anticipating the batsman’s shot and positioning himself beforehand—it saves time and effort.

In the web world, a cache stores frequently accessed data locally, so your browser doesn’t need to fetch it repeatedly, speeding up your browsing experience.

I HOPE THESE CONCEPTS WILL BE REMEMBERED WHENEVER YOU WATCH CRICKET NEXT TIME AND IT REMINDS YOU OF HOW INTERNET WORKS