User avatar Bstran

Translation changed
Servers send responses, which contain a [@https://tools.ietf.org/html/rfc7231#section-6 status-code], [@https://tools.ietf.org/html/rfc7230#section-3.1.2 reason-phrase], and [@https://tools.ietf.org/html/rfc7230#section-2.6 HTTP-version]. The reason phrase is [@https://tools.ietf.org/html/rfc7230#section-3.1.2 obsolete]: clients SHOULD ignore the reason-phrase content. Here is a response which includes a body. The special [@https://tools.ietf.org/html/rfc7230#section-3.3.2 Content-Length] field informs the remote host of the size of the body which follows.
Servers send responses, which contain a服务器发送的响应包含 [@https://tools.ietf.org/html/rfc7231#section-6 status-code], 状态码]、[@https://tools.ietf.org/html/rfc7230#section-3.1.2 reason-phrase], and原因短语] 以及 [@https://tools.ietf.org/html/rfc7230#section-2.6 HTTP-version]. The reason phrase is 版本]。其中，原因短语已被 [@https://tools.ietf.org/html/rfc7230#section-3.1.2 obsolete]: clients SHOULD ignore the reason-phrase content. Here is a response which includes a body. The special [@https://tools.ietf.org/html/rfc7230#section-3.3.2 Content-Length] field informs the remote host of the size of the body which follows.废弃]，客户端应忽略其内容。
06/16/2026
User avatar Bstran

Translation changed
Responses
Responses响应
06/16/2026
User avatar Bstran

Translation changed
This request has a method of "GET", a target of "/", and indicates HTTP version 1.1. It contains a single field called "User-Agent" whose value is "Beast". There is no message body.
This request has a method of "GET", a target of "/", and indicates HTTP version 1.1. It contains a single field called "User-Agent" whose value is "Beast". There is no message body.该请求的方法为 `"GET"`，目标为 `"/"`，并指定使用 HTTP 版本 1.1。该请求包含一个名为 `"User-Agent"` 的字段，其值为 `"Beast"`，且不包含消息体。
06/16/2026
User avatar Bstran

Translation changed
GET / HTTP/1.1\r\n
User-Agent: Beast\r\n
\r\n
GET / HTTP/1.1\r\n
User-Agent: Beast\r\n
\r\n
06/16/2026
User avatar Bstran

Translation changed
Clients send requests, which contain a [@https://tools.ietf.org/html/rfc7230#section-3.1.1 method] and [@https://tools.ietf.org/html/rfc7230#section-5.3 request-target], and [@https://tools.ietf.org/html/rfc7230#section-2.6 HTTP-version]. The method identifies the operation to be performed while the target identifies the object on the server to which the operation applies. The version is almost always 1.1, but older programs sometimes use 1.0.
Clients send requests, which contain a客户端发送的请求包含 [@https://tools.ietf.org/html/rfc7230#section-3.1.1 method] and 方法]、[@https://tools.ietf.org/html/rfc7230#section-5.3 request-target], and请求目标] 以及 [@https://tools.ietf.org/html/rfc7230#section-2.6 HTTP-version]. The method identifies the operation to be performed while the target identifies the object on the server to which the operation applies. The version is almost always 1.1, but older programs sometimes use 版本]。方法指明要执行的操作，目标则指明该操作作用于服务器上的哪个对象。版本号通常为 1.1，但较旧的程序有时仍使用 1.0.。
06/16/2026
User avatar Bstran

Translation changed
Requests
要请求
06/16/2026
User avatar Bstran

Translation changed
Requests
Requests要求
06/16/2026
User avatar Bstran

Translation changed
Every message contains a set of zero or more field name/value pairs, collectively called "fields". The names and values are represented using text strings with various requirements. A serialized field contains the field name, then a colon followed by a space (`": "`), and finally the field value with a trailing CRLF.
Every message contains a set of zero or more field name/value pairs, collectively called "fields". The names and values are represented using text strings with various requirements. A serialized field contains the field name, then a colon followed by a space (`": "`), and finally the field value with a trailing每条消息都包含零个或多个字段，每个字段由字段名和字段值组成，统称为“字段”。字段名和字段值以文本字符串表示，并需满足各项特定要求。序列化后的字段格式为：字段名后跟冒号和空格（`: `），接着是字段值，并以 CRLF. 结尾。
06/16/2026
User avatar Bstran

Translation changed
A request or response is an [@https://tools.ietf.org/html/rfc7230#section-3 HTTP message] (referred to hereafter as "message") having two parts: a header with structured metadata and an optional variable-length body holding arbitrary data. A serialized header is one or more text lines where each line ends in a carriage return followed by linefeed (`"\r\n"`). An empty line marks the end of the header. The first line in the header is called the ['start-line]. The contents of the start line contents are different for requests and responses.
A request or response is an [@https://tools.ietf.org/html/rfc7230#section-3 HTTP message] (referred to hereafter as "message") having two parts: a header with structured metadata and an optional variable-length body holding arbitrary data. A serialized header is one or more text lines where each line ends in a carriage return followed by linefeed (`"\r\n"`). An empty line marks the end of the header. The first line in the header is called the ['start-line]. The contents of the start line contents are different for requests and responses.请求或响应统称为 HTTP 消息（以下简称“消息”），由两部分组成：包含结构化元数据的头部，以及一个可选的、长度可变的消息体，用于承载任意数据。序列化后的头部由一行或多行文本组成，每行以回车换行符（`"\r\n"`）结尾。一个空行用于标识头部的结束。头部的第一行称为起始行，起始行的具体内容在请求和响应中有所不同。
06/15/2026
User avatar Bstran

Translation changed
The HTTP protocol defines the [@https://tools.ietf.org/html/rfc7230#section-2.1 client and server roles]: clients send requests and servers send back responses. When a client and server have established a connection, the client sends a series of requests while the server sends back at least one response for each received request in the order those requests were received.
The HTTP protocol defines the [@https://tools.ietf.org/html/rfc7230#section-2.1 client and server roles]: clients send requests and servers send back responses. When a client and server have established a connection, the client sends a series of requests while the server sends back at least one response for each received request in the order those requests were received.协议定义了客户端和服务器的角色：客户端发送请求，服务器返回响应。当客户端与服务器建立连接后，客户端会连续发送多个请求，服务器则按照收到请求的顺序，为每个请求至少返回一个响应。
06/15/2026
User avatar Bstran

Translation changed
Protocol Primer
Protocol Primer协议入门
06/15/2026
User avatar Bstran

Contributor joined
Contributor joined 06/15/2026
User avatar None

Alert triggered
Repository has changes. 06/12/2026
User avatar None

Alert triggered
Repository has changes. 06/11/2026
User avatar None

Alert triggered
Repository has changes. 06/06/2026
User avatar admin

Resource updated
File “doc/qbk/04_http/01_primer_zh_Hans.qbk” was added. 06/05/2026
User avatar admin

String added in the repository
The Upgrade header field provides a mechanism to transition from HTTP/1.1 to another protocol on the same connection. For example, it is the mechanism used by WebSocket's initial HTTP handshake to establish a WebSocket connection.
The Upgrade header field provides a mechanism to transition from HTTP/1.1 to another protocol on the same connection. For example, it is the mechanism used by WebSocket's initial HTTP handshake to establish a WebSocket connection.
06/05/2026
User avatar admin

String added in the repository
[@https://tools.ietf.org/html/rfc7230#section-6.7 [*`Upgrade`]]
[@https://tools.ietf.org/html/rfc7230#section-6.7 [*`Upgrade`]]
06/05/2026
User avatar admin

String added in the repository
This optional field lists the names of the sequence of transfer codings that have been (or will be) applied to the content payload to form the message body.

Beast understands the "chunked" coding scheme when it is the last (outermost) applied coding. The library will automatically apply chunked encoding when the content length is not known ahead of time during serialization, and the library will automatically remove chunked encoding from parsed messages when present.
This optional field lists the names of the sequence of transfer codings that have been (or will be) applied to the content payload to form the message body.

Beast understands the "chunked" coding scheme when it is the last (outermost) applied coding. The library will automatically apply chunked encoding when the content length is not known ahead of time during serialization, and the library will automatically remove chunked encoding from parsed messages when present.
06/05/2026
User avatar admin

String added in the repository
[@https://tools.ietf.org/html/rfc7230#section-3.3.1 [*`Transfer-Encoding`]]
[@https://tools.ietf.org/html/rfc7230#section-3.3.1 [*`Transfer-Encoding`]]
06/05/2026

Search