In the fast-paced world of technology, we often encounter a whirlwind of terms and phrases that sound complex and intimidating. These technical words, often referred to as tech jargon, are like a secret language that tech professionals use to communicate intricate concepts in a compact way. But for someone outside the tech bubble—or even those just starting their tech journey—this jargon can feel like a barrier.

In this blog, we'll break down some of the most common tech jargon, explain their meanings in simple terms, and explore how they fit into our everyday lives. Whether you’re a tech enthusiast, a professional, or just curious about the digital world, this guide will help demystify the terms and make tech more approachable.

1. HTTP (HyperText Transfer Protocol)

What is HTTP:

HTTP is a protocol (set of rules), which means it’s a set of rules that dictate how data is exchanged between a client (e.g., a web browser) and a server over the internet. When you enter a website URL into your browser, the browser sends an HTTP request to the server hosting that site. The server then responds with the content of the webpage (e.g., HTML, CSS, images, etc.).

Breakdown the HTTP:

1. HyperText:

HyperText is the text that is linked to other document or resources to enabling the user to jump between document and resources to help user seamlessly.

2. Transfer:

Transfer indicates the process of sending and receiving data

A client sending a request to a server to fetch a webpage, an image, or other resources

A server sending a response back to the client containing the requested resources or an error message.

3. Protocol:

In HTTP, the protocol establishes the rules for:

How data is requested (by the client) and sent (by the server).
How messages are formatted and interpreted (e.g., requests, responses).
How connections are managed, such as whether the communication persists after the request or is closed immediately.

STATELESS PROTOCOL:

HTTP IS A STATELESS PROTOCOL:

Means every request is sent by the user to server is independant and information is not retained the information about the previous request . everytime you visit a page you are considered as a new user.

This is the challenge for a stateless protocol for overcome this problem

cookies
sessions
tokens are introduced.

HTTP HEADERS:

HEADERS: JUST LIKE AN INFORMATION :

HEADERS CONTAIN:

1. CLIENT

2.Browser info

3. Date and Time

4. cookie to store

Why we need this type of information??

Imagine you run a website, and you want to promote your mobile app to visitors who access your site using Safari on iOS devices. By analyzing the User-Agent header in the HTTP request, you can determine the client’s browser and operating system.

Based on this header, your server detects that the user is browsing from Safari on iOS.
The server responds with a webpage that includes a pop-up ad encouraging the user to download your mobile app:
- Example: "Enjoy a smoother experience on our app! [Download Now]"

COOKIES:

Cookies are small pieces of data stored on a user’s device (browser) by a website to remember information about the user between sessions. They enable websites to provide a personalized and efficient experience by retaining user-specific details like login sessions, preferences, and browsing history.

HOW COOKIES WORK??

Set by the Server:
- A server sends cookies to the browser via the Set-Cookie HTTP header.
- Example:
```
  httpCopy codeSet-Cookie: session_id=abc123; Path=/; HttpOnly; Secure; SameSite=Lax
```
Stored by the Browser:
- The browser stores the cookie based on its properties, such as expiration time.
Sent with Requests:
- For subsequent requests, the browser automatically includes the cookie in the Cookie HTTP header.
- Example:
```
  httpCopy codeCookie: session_id=abc123
```

REQUEST-RESPONSE MODEL:

Client Sends Request: The client initiates the process by sending a request to a server.

Server Processes the Request: The server processes the incoming request based on the information provided (such as URL, headers, parameters).
Server Sends Response: After processing the request, the server sends an appropriate response back to the client.
Client Handles Response: The client interprets the response and takes action, like displaying content, updating the UI, or logging the user in.

METHOD:

1. GET METHOD:

The GET method is used to retrieve data from the server without modifying it. It is considered safe and idempotent, meaning that making multiple identical GET requests will always produce the same result and will not change the server’s state.

2. POST METHOD

The POST method is used to send data to the server, typically to create or modify a resource. It is not idempotent, meaning that sending the same POST request multiple times may result in different outcomes (e.g., creating multiple resources).

DELETE METHOD

The DELETE method is used to delete a specified resource from the server. It is idempotent, meaning that making the same DELETE request multiple times will have the same effect (i.e., the resource will be deleted once and will not affect the server further).

Response code:

2xx (Successful):

200 OK : The request was successful, and the server sent the requested data.
201 CREATED: The request was successful, and a new resource was created.

3xx (Redirection):
- 301 Moved Permanently: The requested resource has been permanently moved to a new URL.
- 302 Found: The requested resource is temporarily located at a different URL.
4xx (Client Error):
- 400 Bad Request: The request was malformed or invalid.
- 404 Not Found : The requested resource could not be found on the server.
- 403 Forbidden: The server refuses to fulfill the request (e.g., lack of permissions).
5xx (Server Error):
- 500 Internal Server Error : A generic error occurred on the server.
- 502 Bad Gateway: The server received an invalid response from another server.
- 503 Service Unavailable: The server is temporarily unavailable.

HTTP/2

HTTP/2 (Hypertext Transfer Protocol version 2) is the second major version of the HTTP network protocol used by the web. It was developed to improve upon HTTP/1.x, addressing several limitations such as performance bottlenecks and inefficiencies in resource loading. HTTP/2 is designed to improve the speed, efficiency, and security of web traffic.

Key Goals of HTTP/2:

Faster page load times
Reduced latency
Better network utilization
Improved handling of multiplexing requests

MULTIPLEXING (MANY FILES AT SAME TIME)

In HTTP/2 if we send one request then server load all the dependencies in one request but in HTTP its load one file in one request.

2. USES COMPRESSION

HTTP/2 uses HPACK, a compression format for headers, to reduce the overhead caused by HTTP headers. Headers are sent as key-value pairs, and HTTP/2 compresses them to minimize the amount of data transmitted.

How it works:

Frequently used headers (such as User-Agent, Content-Type) are compressed and sent in smaller chunks.
Headers that have been sent previously can be re-used without retransmission.

Benefit:

Reduced Overhead: Smaller header sizes improve performance, especially when dealing with repeated requests.

3.USES ENCRYPTION

HTTP/2 is often used in conjunction with TLS (Transport Layer Security) to encrypt communication between the client and server, ensuring secure data transmission.

Decode Tech Jargons - Simplifying the Language of Technology