Networking Jargons

Networking Jargons

Prasanna Achar's photo
Prasanna Achar
·

6 min read

HTTP (Hyper Text Transfer Protocol):

Most seen protocol in the web world. This is a set of rules and regulations that set for web pages and Web sites for Hyper Text internet.

Protocol: Protocol means Set of rules.

Hyper Text: This means Web documents.

Why use HTTP?

HTTP is not just a set of protocols, it helps developers understand how to build and tracking data and encrypting the private data like cookies. As we all know the bike names NS, KTM or any other but we don’t know the working or name of the engine, It is the heart of the bike but still we know them as their respective name. It is same as with HTTP because we don’t know real name of the website because the machine saves web page name in numbers, But with help of DNS (Domain name System) in HTTP it’s easy to read.

  • Human Readable

  • Network tab visibility

  • Inspect

  • Pages source

DNS: Domain Name System in HTTP is a program to convert the IP address int Human readable address.

Stateless Protocol:

Stateless Protocols used to doesn’t ensure the status of your activity in a particular web site.

State Protocols used to ensure the status of your activity in a particular web site.

It’s like going on a journey on a bike even if you didn’t reach the destination, you take breaks for dinner or for anything, But That doesn’t mean you stopped your journey. That means your journey is going on or ongoing.

Same in HTTP States, where you store your logged in status in session. May be you don’t know that but the website knows your logged in already, So why waste the energy on log in on every moment you open a web sites.

You will hear session and Cookie in developer journey.

Session: Session is used store the status of process.

Cookie: Cookie is key value pair of object where it helps to interact with server and client

HTTP Headers:

  • Client : Client refers to the user of the website.

  • Browser Info: Browsing history.

  • Date and Time

  • Cookie to Store

Request and Response Model:

Request: Request is nothing but a user trying access a web page using browser or searching your website url.

Response: Server response to the request by giving access to visit that website that user clicked.

Type of Request:

  1. GET

  2. POST

  3. DELETE

  4. UPDATE

Response Code:

100: Informational

These codes indicate that the request has been received and the process is continuing.

  • 100 Continue: The client can continue with the request.

  • 101 Switching Protocols: The server is switching to a different protocol as requested by the client.

200: Success

These codes indicate that the request was successfully received, understood, and accepted.

  • 200 OK: The request was successful.

  • 201 Created: The request was successful, and a new resource was created.

  • 202 Accepted: The request has been accepted for processing but is not yet complete.

  • 204 No Content: The server successfully processed the request, but there's no content to return.

300: Redirection

These codes indicate that further action is needed to complete the request.

  • 301 Moved Permanently: The resource has been permanently moved to a new URL.

  • 302 Found: The resource is temporarily located at a different URL.

  • 304 Not Modified: The resource has not been modified since the last request.

  • 307 Temporary Redirect: The request should be repeated with a different URL, but the original method should be used.

400: Client Error

These codes indicate that the request contains bad syntax or cannot be fulfilled.

  • 400 Bad Request: The server could not understand the request due to invalid syntax.

  • 401 Unauthorized: Authentication is required to access the resource.

  • 403 Forbidden: The server understood the request but refuses to authorize it.

  • 404 Not Found: The requested resource could not be found.

  • 408 Request Timeout: The server timed out waiting for the request.

500: Server Error

These codes indicate that the server failed to fulfill a valid request.

  • 500 Internal Server Error: The server encountered an unexpected condition.

  • 501 Not Implemented: The server does not support the functionality required to fulfill the request.

  • 502 Bad Gateway: The server received an invalid response from an upstream server.

  • 503 Service Unavailable: The server is temporarily unable to handle the request.

  • 504 Gateway Timeout: The server did not receive a timely response from an upstream server.

HTTP/2

  • Http means Http2. Http2 uses Http1.1 for fallback.

  • Http1.0 in not publicly available.

  • Http2 Uses comprehension means It uses major of the features of the Http1.1 like Children inheriting Parents behavior.

  • Uses Multiplexing Means It can access or transfer many files and many kinds of files such as .png, jpeg, mp3, mp4, pdf, ppt, pptx, pbix etc.

  • Uses Encryption, It’s nothing but a security layer.

TCP (Transmission Control Protocol)

  • A connection-oriented protocol that ensures reliable transmission of data between devices over a network.

  • Features:

    • Data is sent and received in an orderly manner.

    • Guarantees delivery of packets (data units).

    • Performs error checking and retransmits lost packets.

  • Used in applications where accuracy is critical, such as:

    • HTTP/HTTPS (web browsing)

    • FTP (file transfer)

    • Email protocols (SMTP, IMAP, POP3)

2. IP (Internet Protocol)

  • A network-layer protocol responsible for addressing and routing data packets between devices across networks.

  • Features:

    • Provides unique IP addresses for devices.

    • Ensures data packets are delivered to the correct destination.

  • Types:

    • IPv4: 32-bit addressing (e.g., 192.168.1.1).

    • IPv6: 128-bit addressing (e.g., 2001:0db8:85a3::8a2e:0370:7334).

3. TCP/IP

  • A suite of communication protocols that combines TCP and IP for reliable data transmission over the internet.

  • TCP handles data reliability and error-checking, while IP handles addressing and routing.

  • It's the foundational protocol for the Internet.

4. UDP (User Datagram Protocol)

  • A connectionless protocol that focuses on speed rather than reliability.

  • Features:

    • No error checking or retransmission.

    • Data is sent as individual packets called datagrams.

  • Used in applications where speed is critical, such as:

    • Streaming (video, audio)

    • Online gaming

    • DNS queries

5. DNS (Domain Name System)

  • A system that translates domain names (like example.com) into their corresponding IP addresses (e.g., 93.184.216.34).

  • Acts as the phonebook of the internet.

  • Key components:

    • DNS Resolver: The client-side service that queries DNS servers.

    • Authoritative DNS Server: Provides the IP address for a domain.

    • Root DNS Server: The top level of the DNS hierarchy.

6. Header

  • A metadata section in data packets used by networking protocols.

  • Purpose:

    • Contains information like source/destination IP addresses, ports, protocol type, packet size, and error-checking codes.

    • Headers are used in both TCP and IP packets.

  • Example (TCP Header fields):

    • Source Port and Destination Port: Identify the communicating processes.

    • Sequence Number: Ensures data is delivered in order.

7. FTP (File Transfer Protocol)

  • A protocol used to transfer files between a client and a server over a network.

  • Features:

    • Supports authentication (username/password).

    • Allows uploading, downloading, renaming, and deleting files.

  • Modes:

    • Active mode: Server connects back to the client.

    • Passive mode: Client initiates both data and control connections.

8. URL (Uniform Resource Locator)

  • A string that specifies the location of a resource on the internet and how to access it.

Thank You for reading this Article. …

networkhttpChaiCode