User avatar Bstran

Translation changed
HTTP Relay __example__
HTTP Relay __example中继转发 __示例__
06/18/2026
User avatar Bstran

Translation changed
When a server receives a [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request], the response should contain the entire header that would be delivered if the method was GET, except that the body is omitted.
When a server receives a当服务器收到 [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request], the response should contain the entire header that would be delivered if the method was GET, except that the body is omitted.请求] 时，响应应包含与 GET 请求相同的完整头部信息，但不包含消息体。
06/18/2026
User avatar Bstran

Translation changed
HEAD response (Server) __example__
HEAD response (Server) __example响应（服务器） __示例__
06/18/2026
User avatar Bstran

Translation changed
The [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request] method indicates to the server that the client wishes to receive the entire header that would be delivered if the method was GET, except that the body is omitted. When a client wishes to receive the response to a HEAD request, it is necessary to inform the parser not to expect a body. This is done by calling [link beast.ref.boost__beast__http__basic_parser.skip `basic_parser::skip`] with the value `true`, as shown in this example:
The [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request] method indicates to the server that the client wishes to receive the entire header that would be delivered if the method was GET, except that the body is omitted. When a client wishes to receive the response to a HEAD request, it is necessary to inform the parser not to expect a body. This is done by calling请求] 方法表示客户端希望服务器返回与 GET 请求相同的头部信息，但不包含消息体。当客户端需要接收 HEAD 请求的响应时，必须告知解析器不需要消息体。这可以通过调用 [link beast.ref.boost__beast__http__basic_parser.skip `basic_parser::skip`] with the value `true`, as shown in this example:并传入 `true` 来实现，如下例所示：
06/18/2026
User avatar Bstran

Translation changed
HEAD request (Client) __example__
HEAD request (Client) __example请求（客户端） __示例__
06/18/2026
User avatar Bstran

Translation changed
The Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Handling the Expect field can be implemented easily in a server by constructing a __parser__ to read the header first, then send an informational HTTP response, and finally read the body using the same parser instance. A synchronous version of this server action looks like this:
The请求中的 Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Handling the Expect field can be implemented easily in a server by constructing a __parser__ to read the header first, then send an informational HTTP response, and finally read the body using the same parser instance. A synchronous version of this server action looks like this:字段若值为 `100-continue`，则具有特殊含义。它表示客户端在发送消息头部之后，希望在发送消息体之前立即收到一个信息性响应。这通常是因为消息体的计算开销较大或数据量较大。[@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 第 5.1.1 节] 对此行为进行了详细说明。在服务器端处理 Expect 字段较为简单：先构造一个 __parser__ 读取头部，然后发送一个信息性 HTTP 响应，最后使用同一个解析器实例读取消息体。以下是一个同步版本的服务器实现：
06/18/2026
User avatar Bstran

Translation changed
Expect 100-continue (Server) __example__
Expect: 100-continue (Server) __example（服务器） __示例__
06/18/2026
User avatar Bstran

Translation changed
The Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Invoking the 100-continue behavior is implemented easily in a client by constructing a __serializer__ to send the header first, then receiving the server response, and finally conditionally send the body using the same serializer instance. A synchronous, simplified version (no timeout) of this client action looks like this:
The请求中的 Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Invoking the 100-continue behavior is implemented easily in a client by constructing a __serializer__ to send the header first, then receiving the server response, and finally conditionally send the body using the same serializer instance. A synchronous, simplified version (no timeout) of this client action looks like this:字段若值为 `100-continue`，则具有特殊含义。它表示客户端在发送消息头部之后，希望在发送消息体之前立即收到一个信息性响应。这通常是因为消息体的计算开销较大或数据量较大。[@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 第 5.1.1 节] 对此行为进行了详细说明。在客户端实现 100-continue 行为比较简单：先构造 __serializer__ 发送头部，然后接收服务器响应，最后根据情况使用同一个序列化器实例发送消息体。以下是一个同步的简化版本（不含超时）的实现：
06/18/2026
User avatar Bstran

Translation changed
Expect 100-continue (Client) __example__
Expect: 100-continue (Client) __example（客户端） __示例__
06/18/2026
User avatar Bstran

Translation changed
This example illustrates how a server may make the commitment of a body type depending on the method verb:
This example illustrates how a server may make the commitment of a body type depending on the method verb:本示例演示服务器如何根据请求方法来决定使用哪种消息体类型：
06/18/2026
User avatar Bstran

Translation changed
Sophisticated servers may wish to defer the choice of the Body template type until after the header is available. Then, a body type may be chosen depending on the header contents. For example, depending on the verb, target path, or target query parameters. To accomplish this, a parser is declared to read in the header only, using a trivial body type such as [link beast.ref.boost__beast__http__empty_body `empty_body`]. Then, a new parser is constructed from this existing parser where the body type is conditionally determined by information from the header or elsewhere.
Sophisticated servers may wish to defer the choice of the Body template type until after the header is available. Then, a body type may be chosen depending on the header contents. For example, depending on the verb, target path, or target query parameters. To accomplish this, a parser is declared to read in the header only, using a trivial body type such as [link beast.ref.boost__beast__http__empty_body `empty_body`]. Then, a new parser is constructed from this existing parser where the body type is conditionally determined by information from the header or elsewhere.高级服务器可能希望等到获取头部信息后，再决定使用哪种 Body 模板类型。这样就能根据头部内容（例如请求方法、目标路径或查询参数）来选用合适的消息体类型。具体做法是：先使用一个简单的消息体类型（如 [link beast.ref.boost__beast__http__empty_body `empty_body`]）声明解析器，只用于读取头部。然后，基于这个已有的解析器构造一个新的解析器，并根据头部或其他信息来确定新解析器的消息体类型。
06/18/2026
User avatar Bstran

Translation changed
Change Body Type __example__
Change Body Type __example修改消息体类型 __示例__
06/18/2026
User avatar Bstran

Translation changed
These examples in this section are working functions that may be found in the examples directory. They demonstrate the usage of the library for a variety of scenarios.
These examples in this section are working functions that may be found in the examples directory. They demonstrate the usage of the library for a variety of scenarios.本节提供的示例均为可运行函数，存放于 examples 目录中。这些示例展示了该库在不同场景下的具体用法。
06/18/2026
User avatar Bstran

Translation changed
HTTP Examples
HTTP Examples示例
06/18/2026
User avatar Bstran

Contributor joined
Contributor joined 06/18/2026
User avatar Bstran

Translation completed
Translation completed 06/18/2026
User avatar Bstran

Translation changed
The basic parser uses virtual functions. To declare your user-defined parser, derive from __basic_parser__ and implement all the required virtual functions. A declaration for the derived class may look like this:
The basic parser uses virtual functions. To declare your user-defined parser, derive from __basic_parser__ and implement all the required virtual functions. A declaration for the derived class may look like this:基本解析器使用虚函数。要声明自定义解析器，需要从 __basic_parser__ 派生并实现所有必需的虚函数。派生类的声明大致如下：
06/18/2026
User avatar Bstran

Translation changed
* Use a container provided by an external interface.
* Use a container provided by an external interface.使用外部接口提供的容器。
06/18/2026
User avatar Bstran

Translation changed
* Inspect incoming header fields and keep or discard them.
* Inspect incoming header fields and keep or discard them.检查传入的头部字段，并决定保留或丢弃。
06/18/2026
User avatar Bstran

Translation changed
While the parsers included in the library will handle a broad number of use-cases, the __basic_parser__ interface can be subclassed to implement custom strategies for storing parsed results: the basic parser processes input buffers into elements according to the HTTP/1 protocol specification, while the derived class decides what to do with those elements. Custom parsers will work with all of the HTTP stream read algorithms, as those algorithms use only the basic parser interface. Some use cases for implementing custom parsers are:
While the parsers included in the library will handle a broad number of use-cases, the __basic_parser__ interface can be subclassed to implement custom strategies for storing parsed results: the basic parser processes input buffers into elements according to the HTTP/1 protocol specification, while the derived class decides what to do with those elements. Custom parsers will work with all of the HTTP stream read algorithms, as those algorithms use only the basic parser interface. Some use cases for implementing custom parsers are:虽然库自带的解析器能覆盖大部分常见场景，但通过继承 __basic_parser__ 接口，也可以实现自定义的解析结果存储策略。基本解析器负责按 HTTP/1 协议规范将输入缓冲区解析为各个元素，而派生类则决定如何处理这些元素。由于所有 HTTP 流读取算法都只依赖基本解析器接口，因此自定义解析器可以与它们协同工作。以下是一些可能需要实现自定义解析器的场景：
06/18/2026

Search