Fundamentals 8 min read

Mastering HTTP & HTML: Core Concepts Every Developer Should Know

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.

MaGe Linux Operations
MaGe Linux Operations
MaGe Linux Operations
Mastering HTTP & HTML: Core Concepts Every Developer Should Know

HTTP: Hyper Text Transfer

HTTP (Hyper Text Transfer Protocol) is the most widely used network protocol on the Internet, defining how WWW files are exchanged. It was originally designed to publish and retrieve HTML pages. The protocol evolved from Ted Nelson's hypertext concept and is standardized in RFC 2616 (HTTP 1.1).

HTML: Hyper Text Markup Language

HTML is a markup language under the Standard Generalized Markup Language (SGML). It allows embedding images, links, audio, and scripts within a page. An HTML document consists of a <head> section providing metadata and a <body> section containing the page content.

<html>
    <head>
        <title>TITLE</title>
    </head>
    <body>
        <h1>H1</h1>
        <p></p>
        <h2>H2</h2>
        <p><a href="admin.html">ToGoogle</a></p>
    </body>
</html>

HTML documents can be generated:

Statically: directly writing the markup.

Dynamically: using server‑side languages such as PHP, JSP, ASP, .NET to output HTML.

Via CGI (Common Gateway Interface), which lets a client request data from programs running on the server.

HTTP header fields are divided into three categories:

General headers (e.g., Connection, Cache-Control).

Request headers (e.g., Client-IP, Host, Referer, User-Agent, Accept family).

Response headers (e.g., Age, Server, Vary, authentication and cookie headers).

Entity headers (e.g., Location, Allow, content‑related headers like Content-Type, caching headers like Etag, Expires).

Extension headers (non‑standard, e.g., X-Forward-For, X-Via).

HTTP request message format:

<method><request-URL><version>
<HEADERS>
<entity-body>

HTTP response message format:

<version><status><reason-phrase>
<HEADERS>
<entity-body>

Key HTTP methods include GET, HEAD, POST, PUT, DELETE, OPTIONS, and TRACE. Status codes are grouped as 1xx (informational), 2xx (success), 3xx (redirection), 4xx (client error), and 5xx (server error).

Web resources are identified by MIME types (e.g., text/html, image/jpeg) and URIs/URLs that specify the scheme, server, and resource path.

Web server I/O models:

Single‑process (serial).

Multi‑process (one process per request).

Thread‑based reuse (one thread per request).

Thread pool handling multiple requests per thread.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

HTTPHTMLweb protocolweb fundamentalsMIME Types
MaGe Linux Operations
Written by

MaGe Linux Operations

Founded in 2009, MaGe Education is a top Chinese high‑end IT training brand. Its graduates earn 12K+ RMB salaries, and the school has trained tens of thousands of students. It offers high‑pay courses in Linux cloud operations, Python full‑stack, automation, data analysis, AI, and Go high‑concurrency architecture. Thanks to quality courses and a solid reputation, it has talent partnerships with numerous internet firms.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.