GET and POST are two of the eight HTTP request methods; this article explains their request‑line, header and body structures, compares their characteristics such as safety, idempotence, caching, length limits and TCP packet usage, and clarifies why HTTP distinguishes them despite sharing the same underlying protocol.
This article explains the complete journey of a web request—from IP addressing, DNS resolution, and CDN acceleration, through TCP stream handling and message framing, to CGI/FastCGI execution, server model choices, and the evolution of data-layer architectures for scalable applications.
This article explains step‑by‑step what occurs when a user types a URL and presses Enter, covering URL parsing, DNS resolution, TCP three‑way handshake and four‑way termination, HTTP request/response formation, and the browser’s rendering process, providing interview‑ready insights into web networking fundamentals.
The article explains why visiting a website by its IP address often results in errors, showing that the HTTP Host header differs from domain‑based requests, and demonstrates this with Fiddler and Postman experiments using Baidu as an example.
This article explains the fundamentals of HTTP GET and POST request methods, detailing their request line, headers, and body structures, illustrating each with real‑world examples and code snippets, and clarifying their safety, idempotence, caching, and practical differences.
This article explains the structure of HTTP request messages, compares the characteristics of GET and POST methods, and provides real-world examples to illustrate how each method works and differs in practice.
When you type a URL and press Enter, the browser performs a series of steps—including URL parsing, DNS resolution across multiple caches, TCP three‑way handshake, HTTP request construction, server processing, and response handling—each involving specific protocols and layers that together deliver the requested web page.
This article explains the concepts and differences of URI, URL, and URN, describes their hierarchical relationship, outlines URL components, discusses Data URI syntax, presents best‑practice guidelines for stable and user‑friendly URL design, and provides real‑world examples such as Flickr API URL patterns.
This note provides a comprehensive overview of HTTP protocol, detailing request and response structures, including headers, body content, status codes, and common pitfalls, supplemented with illustrative screenshots and links for further reading.
The article explores the origins of the HTTP 404 status code, debunks the legend of CERN's Room 404, recounts mysterious flights named 404, and ties these stories together to explain why the error has become a cultural symbol of missing content.
This article walks through the complete journey of a web request—from entering a URL, checking browser, OS, router, and ISP DNS caches, performing DNS queries, resolving MAC addresses via ARP, establishing a TCP three‑way handshake, sending an HTTP request, to finally rendering the HTML page in the browser.
This article explains the core characteristics of the HTTP protocol—including its flexibility, reliability, application‑layer nature, request‑response model, and statelessness—and then details short and long connection management, related header fields, head‑of‑line blocking, and practical performance‑enhancing techniques such as concurrent connections and domain sharding.
This article explains HTTP's core characteristics—flexibility, reliability, application‑layer nature, request‑response model, and statelessness—then dives into short‑ and long‑connection management, head‑of‑line blocking, and practical optimization techniques such as concurrent connections and domain sharding.
This article explores what “state” means in the HTTP protocol, clarifies the concepts of statelessness and connection‑lessness, demonstrates their impact through a simulated shopping‑cart scenario, and explains how cookies and sessions introduce state to enable practical web interactions.
This article explores what “state” means in the HTTP protocol, clarifying the concepts of statelessness, the role of cookies and sessions, and how they address the limitations of pure HTTP through practical examples and security considerations.
This article explores the true meaning of HTTP’s stateless nature, clarifies common misconceptions, examines how cookies and sessions add state, and demonstrates through a simulated shopping scenario why additional mechanisms are needed to maintain user context across requests.
This article provides a concise overview of the most frequently used HTTP status codes, explaining the meaning of each 1xx, 2xx, 3xx, 4xx, and 5xx series and detailing individual codes such as 200, 201, 301, 404, and 500 to help developers interpret server responses correctly.
This article explains how HTTP relies on TCP/IP, describes the browser's steps to open a TCP connection, details TCP segment and IP packet structures, outlines socket API calls, and discusses TCP handshake, slow start, and HTTP connection techniques such as parallel, persistent, and pipelined connections.
This article explains the origin, purpose, and inner workings of HTTP cookies, details their attributes and security implications, demonstrates how to create, retrieve, and set cookies with Python's requests library, and compares cookies with server‑side sessions for robust web development.
This article explains what HTTP cookies are, their basic operation via Set‑Cookie and Cookie headers, the standard cookie format and attributes, how to view them in browsers, and how cookies enable seamless cross‑domain redirects, illustrated with PHP code examples.
The article explains step‑by‑step what occurs when a user types a URL, covering DNS resolution, browser caching, HTTP requests and redirects, server processing, HTML generation, resource fetching, compression, and asynchronous AJAX communication, using Facebook as a concrete example.
This article walks through the complete journey of a web request—from entering a URL, DNS resolution, TCP three‑way handshake, HTTP request and response, to the browser’s parsing, layout, and painting processes—explaining each step and the underlying protocols in clear detail.
This article walks through the complete lifecycle of a web request—from entering a URL, DNS resolution, and HTTP communication, to server processing, HTML delivery, resource fetching, and AJAX interactions—explaining each step with diagrams and code examples.
This article walks through every step from pressing a key on the keyboard to the browser rendering a web page, covering hardware signaling, kernel interrupt handling, DNS resolution, TCP handshakes, HTTP exchange, and final page display, illustrating how many university‑level concepts intersect in a single URL request.
This article explains what a web crawler (spider) is, how browsers retrieve pages, and clarifies the concepts and structures of URIs and URLs with examples, highlighting why accurate URL understanding is crucial for building effective crawlers.
In this whimsical interview, the aging Internet Explorer, Firefox, and Chrome discuss their rivalry, the evolution of browsers, how they fetch web pages via HTTP requests and responses, status codes, cookies, and the challenges of modern web technologies, offering a clear overview of web fundamentals.
From typing a URL to rendering a page, this article walks through each step—browser DNS lookup, HTTP request and response, redirects, server processing, content delivery, and asynchronous calls—revealing the complex interactions that make modern web browsing possible.
This article explains the fundamentals of HTTP and HTML, covering protocol definitions, request and response structures, header categories, methods, status codes, HTML document structure, static and dynamic generation, MIME types, URI/URL formats, and web server I/O models.
This article walks through every step that occurs when you type a URL— from the browser’s DNS lookup and HTTP request, through server processing, redirects, HTML rendering, and subsequent resource and AJAX calls—revealing how browsers, servers, and CDNs cooperate to deliver a web page.
This article explores the origin and purpose of the “www” prefix in web addresses, detailing domain hierarchy, early internet service separation, modern usage conventions, and the cultural significance of linking within the World Wide Web.
