惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

量子位
I
InfoQ
人人都是产品经理
人人都是产品经理
博客园 - 三生石上(FineUI控件)
爱范儿
爱范儿
Hugging Face - Blog
Hugging Face - Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
S
SegmentFault 最新的问题
美团技术团队
小众软件
小众软件
Blog — PlanetScale
Blog — PlanetScale
Jina AI
Jina AI
aimingoo的专栏
aimingoo的专栏
H
Help Net Security
Last Week in AI
Last Week in AI
博客园_首页
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
L
LangChain Blog
云风的 BLOG
云风的 BLOG
Martin Fowler
Martin Fowler
宝玉的分享
宝玉的分享
G
Google Developers Blog
博客园 - 叶小钗
博客园 - Franky

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Understanding HTTP
Rahul kumar · 2026-05-16 · via DEV Community

Hey!! there reader, Today in this blog we will explore What is HTTP? , Explore HTTP .If you don’t know anything or want to revise this blog will help a lot.

Introduction

HTTP (Hypertext transfer protocol) is one of the many protocol which is used to communicate on the application layer of the TCP/IP model over the internet and between different computers . It is a set of rules and format that is used as a standard set of practices while communicating. HTTP have statelessness which is it does not remember the previous request or persists and data during communication. It follows the client-server architecture which is when user requests a resource, the response is provided in specified format by the server. The request and response should contain headers which provide metadata about the provided body and a body which is the actual data sent by the client or requested by the client. The HTTP contains specified set of OPERATION names known as HTTP methods which are used to specify the server about the type of request.

Also server uses codes which are known as HTTP Status codes to specify the type or state of the response. Let’s start from the HTTP headers.

HTTP Headers

The headers are the metadata that contains the information about the data, like requested source, destination, user-agent , tokens , e-tags , date-times , status codes. These headers are created and often used on the client side or the server side to validate authorize or permit specific tasks from the user. There are different types of headers.

  1. Request Header : Sent by the client to the server.
  2. Response Header : Sent by the server to the client.
  3. Representation Header : Decides the format of the response or the request body to be sent.
  4. Payload Header: This are the custom headers used by the server or client to authenticate and authorize or for any different task used by the developer for specific tasks or requirements.

Covering all the headers then we think how the HTTP communicate and be able to do basic CRUD operations. We understand HTTP methods.

HTTP Methods

The HTTP Methods are the basic set of operations format that helps the server understand the type of the request like for example, If it is creating , updating or deleting a resource. These methods are used such operation each having a specific work.These is mostly invoked from the client side to request some resources and can be found in the request headers.

The HTTP Methods are:

  1. GET : Used to retrieve a source from the server.
  2. POST: Used to add new data to the server.
  3. PATCH: Partially updates the data without removing them. In other words add more data to the already existing data.
  4. PUT: Completely replaces the old data to the new data sent.
  5. DELETE: Delete a resource from the server.

These are the most commonly used methods in the modern development and use case. But there are some other methods which are not most frequently used.

Those are:

  1. HEAD: Used to only see the headers no body.
  2. OPTIONS: Provides the available methods for the specific endpoint.
  3. TRACE: Loopback test provides the same data again to check if it is working properly.

The most common HTTP methods among them are GET and POST which are most frequently used in any application to give and take data.

Then comes the HTTP status code which is sent by the server on the response headers.

HTTP Status Codes

These codes have specific meaning to each of the response codes and have different range for what the response provided by the server upon your request. It is standard practice to maintain the response with a status code specific to the response.The Range starts from 100 to 599

The Ranges specify what type of information is shared.

  1. 100 - 199 : Informational response
  2. 200 - 299 : Success response
  3. 300 - 399 : Redirection response
  4. 400 - 499 : Client side error
  5. 500 - 599 : Server side error

The status code each represents a specific response type and among the most commonly used status code are:

  1. 100 : Continue
  2. 102 : Processing
  3. 200 : OK
  4. 201 : Created
  5. 202 : Accepted
  6. 307 : Temporary redirect
  7. 308 : Permanent redirect
  8. 400 : Bad request
  9. 401 : Unauthorized
  10. 402 : Payment required
  11. 404 : Not found
  12. 500 : Internal server error
  13. 504 : Gateway timeout

These are the most commonly used status codes across all the ranges and most of the work is done in these only.

Conclusion

These are most of the cover ups of HTTP basics , although you maybe wondering “But nowadays we are using HTTPS not HTTP then what is the diffrence between two if they work in the same way”, There is a big diffrence not in the form of communication but in the way of communication.

The S in HTTPS stands for secure so it is Hypertext transfer protocol secure , In normal works it means the data packets that were sent over the network are secured , Now lets understand the process of how it gets secure.

Previously on HTTP the data packets were shared over the network raw so anybody that interprets the network can access it and change the data and this was one of the core reason why the TSL and and later SSL were introduced. These are the extra layer that were used to encrypt the data and when they are being transported from the server to the client and can only be decoded from the client side which have they key to decrypt the message usign the specified salt and key value.

Understanding the TLS and SSL are a completely diffrent topics and cannot be covered in this blog. And thus using these layers we can convert HTTP to HTTPS, Which is highly recommended in today’s time.

This is the conclusion for the HTTP Basics I have tried to cover almost everything that is required for basic knowledge and understanding. If left anything please provide feedback on how the blog was. Thank you for reading.