HTTP 有哪些内容？
互联网建立在协议的基础之上，而万维网通信的核心正是超文本传输协议（HTTP）。它是我们访问网站、发送数据以及与在线服务交互的支柱。但除了 GET 请求和状态码的基本机制之外，还有许多隐藏的宝藏、细微差别和鲜为人知的特性，它们驱动着我们所熟知的网络。最近 Hacker News 上的一篇帖子引起了对深入探讨这一常被低估的网页开发方面的资源的关注：What's on HTTP?。
这篇 Hacker News 上的帖子获得了适度但热情的回应，它突出展示了一个致力于探索 HTTP 各个要素的网站，这些要素使 HTTP 能够正常运作。从管理数据交换的基本头部到连接管理的晦涩细节，这个资源全面地展示了塑造我们在线体验的协议。但是什么让 HTTP 如此引人入胜？为什么开发者和爱好者都应该关心它的复杂性？
HTTP 的层次结构
从本质上讲，HTTP 是一种无状态协议，旨在通过互联网传输超文本。它运行在 TCP/IP 协议套件之上，依赖于较低级别的协议来处理实际的数据传输。理解 HTTP 不仅仅是知道如何发送请求；它还在于理解允许我们构建复杂网页应用程序的抽象层次。
HTTP 最关键的一个组成部分是头部。头部是键值对，它们提供了关于请求或响应的元数据。它们包括关于内容类型、缓存策略、认证方法等信息。例如，Content-Type 头部指定了发送的数据的媒体类型，而 Authorization 头部可以携带访问受保护资源的凭证。
以下是一个请求中头部如何工作的简单示例：
GET /api/users HTTP/1.1
Host: example.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36
Accept: application/json
Authorization: Bearer token123
在这个请求中，客户端正在请求 example.com 上 /api/users 端点的数据。头部提供了上下文：客户端浏览器的信息、它可以处理的内容类型，以及一个用于访问 API 的授权令牌。
HTTP 方法：不仅仅是 GET 和 POST
虽然大多数开发人员熟悉基本的 HTTP 方法——GET、POST、PUT、DELETE，但还有更丰富的 HTTP 方法可以用来构建更表达性和高效的 API。每种方法都服务于特定的目的：
GET：从服务器检索数据。POST：将数据提交到服务器进行处理。PUT：更新或替换服务器上的资源。DELETE：从服务器删除资源。HEAD：类似于 GET，但仅检索头部，不检索正文。OPTIONS：描述目标资源的通信选项。PATCH：对资源应用部分修改。TRACE：沿路径到目标资源执行消息回环测试。
使用正确的 HTTP 方法对于维护 API 的语义至关重要。例如，使用 PUT 来创建新资源而不是 POST 可能会导致混淆和意外的行为。OPTIONS 方法对于发现服务器上可用的方法特别有用，这对于探索 API 的开发人员非常有帮助。
状态码：解码网络的语言
HTTP 状态码提供了关于请求结果的反馈。它们被分为以下几类：
- 1xx：信息性——请求已收到，正在继续处理。
- 2xx：成功——操作已成功收到、理解并接受。
- 3xx：重定向——需要进一步操作才能完成请求。
- 4xx：客户端错误——请求包含错误语法或无法完成。
- 5xx：服务器错误——服务器未能满足一个明显有效的请求。
熟悉状态码对于调试和理解 API 行为至关重要。例如，404 Not Found 表示请求的资源不存在，而 500 Internal Server Error 表示服务器端出了问题。以下是一个典型的 404 响应的样子：
HTTP/1.1 404 Not Found
Date: Mon, 27 Sep 2021 12:00:00 GMT
Server: Apache/2.4.41 (Ubuntu)
Content-Type: text/html; charset=UTF-8
Content-Length: 175
<html>
<head><title>404 Not Found</title></head>
<body>
<h1>404 Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body>
</html>
在这个响应中，服务器通知客户端请求的 URL 在此服务器上不存在。响应包括标准头部和一个简单的 HTML 正文来解释错误。
HTTP 的隐藏宝藏
除了基础知识之外，HTTP 还有几个鲜为人知的特性，在正确利用时可以非常实用。以下是一些例子：
条件请求
条件请求允许客户端通过依赖服务器当前状态来发送请求，从而减少不必要的数据传输。可以使用 If-None-Match 和 If-Modified-Since 等头部来检查资源是否自上次请求以来已更改。如果资源没有更改，服务器可以响应 304 Not Modified 状态，从而节省带宽。
范围请求
范围请求允许客户端仅请求资源的一部分，这对于分块下载大文件或流式传输媒体非常有用。Range 头部指定了要返回的字节范围，如果请求有效，服务器会以 206 Partial Content 状态响应。
Cookies 和会话管理
Cookies 是存储在客户端浏览器上的小数据片段，用于跨多个请求维护状态。它们对于会话管理、用户认证和个性化至关重要。Set-Cookie 和 Cookie 头部用于发送和接收 Cookies。
缓存
缓存是 HTTP 的一个关键方面，它可以提高性能并减少服务器负载。Cache-Control、Expires 和 ETag 等头部定义了缓存策略。通过利用缓存，开发人员可以最小化延迟和带宽使用，从而提升用户体验。
你为什么要关心？
理解 HTTP 不仅仅是后端开发人员的任务；对于任何与网页工作的人员都有益处。前端开发人员需要了解请求和响应的工作原理，以便调试问题并优化性能。DevOps 工程师应该了解 HTTP，以便配置负载均衡器并排除网络问题。即使是最终用户，对 HTTP 有一基本的了解也能更好地理解网站如何运作并排除连接问题。
资源 What's on HTTP? 是任何希望深入了解协议的人的宝藏。它不仅仅是一个特性列表；它是一份指南，说明了 HTTP 如何融入更大的网页开发图景。无论你是经验丰富的开发人员还是初学者，这个资源都可以提供宝贵的见解，了解网页的机制。
总结
HTTP 不仅仅是一种传输数据的协议；它是一个复杂且细致的系统，是整个网络的基石。通过理解它的复杂性——头部、方法、状态码和隐藏特性——我们可以构建更高效、更健壮、更用户友好的应用程序。像 What's on HTTP? 这样的资源对于任何希望更深入理解网络基础技术的人来说都是无价的。无论是调试 API、优化性能，还是仅仅好奇互联网如何运作，深入研究 HTTP 都能提供丰富的知识和实用的见解。
What's on HTTP?
The internet is built on a foundation of protocols, and at the heart of web communication lies the Hypertext Transfer Protocol (HTTP). It's the backbone of how we access websites, send data, and interact with online services. But beyond the basic mechanics of GET requests and status codes, there's a fascinating world of hidden gems, nuances, and little-known features that power the web as we know it. A recent thread on Hacker News brought attention to a resource that dives deep into this often-underestimated aspect of web development: What's on HTTP?.
The post on Hacker News, which garnered a modest but enthusiastic response, highlights a site dedicated to exploring the various elements that make HTTP tick. From the essential headers that govern data exchange to the arcane details of connection management, this resource offers a comprehensive look at the protocol that shapes our online experience. But what makes HTTP so intriguing, and why should developers and enthusiasts alike care about its intricacies?
The Layers of HTTP
At its core, HTTP is a stateless protocol designed for transferring hypertext over the internet. It operates on top of the TCP/IP suite, relying on lower-level protocols to handle the actual data transmission. Understanding HTTP isn't just about knowing how to send a request; it's about appreciating the layers of abstraction that allow us to build complex web applications.
One of the most critical components of HTTP is the header. Headers are key-value pairs that provide metadata about the request or response. They include information about content types, caching policies, authentication methods, and much more. For example, the Content-Type header specifies the media type of the data being sent, while the Authorization header can carry credentials for accessing protected resources.
Here's a simple example of how headers work in a request:
GET /api/users HTTP/1.1
Host: example.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36
Accept: application/json
Authorization: Bearer token123
In this request, the client is asking for data from the /api/users endpoint on example.com. The headers provide context: the client's browser information, the type of content it can handle, and an authorization token to access the API.
HTTP Methods: More Than Just GET and POST
While most developers are familiar with the basic HTTP methods—GET, POST, PUT, DELETE—there's a richer set of methods that can be used to build more expressive and efficient APIs. Each method serves a specific purpose:
GET: Retrieve data from a server.POST: Submit data to be processed to a server.PUT: Update or replace a resource on the server.DELETE: Remove a resource from the server.HEAD: Similar to GET, but only retrieves headers, not the body.OPTIONS: Describe communication options for the target resource.PATCH: Apply partial modifications to a resource.TRACE: Perform a message loop-back test along the path to the target resource.
Using the correct HTTP method is crucial for maintaining the semantics of your API. For instance, using PUT to create a new resource instead of POST can lead to confusion and unintended behavior. The OPTIONS method is particularly useful for discovering available methods on a server, which can be helpful for developers exploring an API.
Status Codes: Decoding the Web's Language
HTTP status codes provide feedback about the outcome of a request. They are grouped into categories:
- 1xx: Informational — Request received, continuing process.
- 2xx: Success — The action was successfully received, understood, and accepted.
- 3xx: Redirection — Further action needs to be taken to complete the request.
- 4xx: Client Error — The request contains bad syntax or cannot be fulfilled.
- 5xx: Server Error — The server failed to fulfill an apparently valid request.
Familiarity with status codes is essential for debugging and understanding API behavior. For example, a 404 Not Found indicates that the requested resource doesn't exist, while a 500 Internal Server Error suggests something went wrong on the server side. Here's how a typical 404 response might look:
HTTP/1.1 404 Not Found
Date: Mon, 27 Sep 2021 12:00:00 GMT
Server: Apache/2.4.41 (Ubuntu)
Content-Type: text/html; charset=UTF-8
Content-Length: 175
<html>
<head><title>404 Not Found</title></head>
<body>
<h1>404 Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body>
</html>
In this response, the server is informing the client that the requested URL doesn't exist. The response includes standard headers and a simple HTML body explaining the error.
The Hidden Gems of HTTP
Beyond the basics, HTTP has several lesser-known features that can be incredibly useful when leveraged correctly. Here are a few:
Conditional Requests
Conditional requests allow clients to reduce unnecessary data transfer by making requests that depend on the current state of the server. Headers like If-None-Match and If-Modified-Since can be used to check if a resource has changed since the last request. If the resource hasn't changed, the server can respond with a 304 Not Modified status, saving bandwidth.
Range Requests
Range requests enable clients to request only a portion of a resource, which is useful for downloading large files in chunks or streaming media. The Range header specifies the byte range to be returned, and the server responds with a 206 Partial Content status if the request is valid.
Cookies and Session Management
Cookies are small pieces of data stored on the client's browser to maintain state across multiple requests. They are essential for session management, user authentication, and personalization. The Set-Cookie and Cookie headers are used to send and receive cookies.
Caching
Caching is a critical aspect of HTTP that improves performance and reduces server load. Headers like Cache-Control, Expires, and ETag define caching policies. By leveraging caching, developers can minimize latency and bandwidth usage, enhancing the user experience.
Why Should You Care?
Understanding HTTP isn't just for backend developers; it's beneficial for anyone working with the web. Frontend developers need to know how requests and responses work to debug issues and optimize performance. DevOps engineers should understand HTTP to configure load balancers and troubleshoot network problems. Even end-users can benefit from a basic grasp of HTTP to better understand how websites function and troubleshoot connectivity issues.
The resource What's on HTTP? is a treasure trove for anyone looking to deepen their knowledge of the protocol. It's not just a list of features; it's a guide to understanding how HTTP fits into the larger picture of web development. Whether you're a seasoned developer or just starting out, this resource can provide valuable insights into the mechanics of the web.
Takeaway
HTTP is far more than just a protocol for transferring data; it's a complex and nuanced system that underpins the entire web. By understanding its intricacies—headers, methods, status codes, and hidden features—we can build more efficient, robust, and user-friendly applications. Resources like What's on HTTP? are invaluable for anyone looking to gain a deeper appreciation of the web's foundational technology. Whether you're debugging an API, optimizing performance, or simply curious about how the internet works, delving into HTTP can provide a wealth of knowledge and practical insights.
