msgid ""
msgstr ""
"Project-Id-Version: Chinese (Simplified Han script) (Boost Beast Translation "
"(zh_Hans))\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-06-07 19:08+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: Chinese (Simplified Han script) <https://"
"insights.cppalliance.org/weblate/projects/boost-beast-documentation-zh_Hans/"
"doc-qbk-04-http--http-qbk/zh_Hans/>\n"
"Language: zh_Hans\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Weblate 2026.5\n"

#. type: section title
#: 10
#, fuzzy
msgid "HTTP"
msgstr "HTTP"

#. type: paragraph
#: 13
#, fuzzy
msgid "Higher level functions such as Basic"
msgstr "Higher level functions such as Basic"

#. type: paragraph
#: 20
#, fuzzy
msgid ""
"This library offers programmers simple and performant models of HTTP "
"messages and their associated operations including synchronous, "
"asynchronous, and buffer-oriented parsing and serialization of messages in "
"the HTTP/1 wire format using __Asio__. Specifically, the library provides:"
msgstr ""
"This library offers programmers simple and performant models of HTTP "
"messages and their associated operations including synchronous, "
"asynchronous, and buffer-oriented parsing and serialization of messages in "
"the HTTP/1 wire format using __Asio__. Specifically, the library provides:"

#. type: variablelist cell
#: 25
#, fuzzy
msgid "Stream Reading"
msgstr "Stream Reading"

#. type: variablelist cell
#: 25
#, fuzzy
msgid ""
"The functions [link beast.ref.boost__beast__http__read `read`], [link "
"beast.ref.boost__beast__http__read_header `read_header`], [link "
"beast.ref.boost__beast__http__read_some `read_some`], [link "
"beast.ref.boost__beast__http__async_read `async_read`], [link "
"beast.ref.boost__beast__http__async_read_header `async_read_header`], and "
"[link beast.ref.boost__beast__http__async_read_some `async_read_some`] read "
"HTTP/1 message data from a [link beast.concepts.streams stream]."
msgstr ""
"The functions [link beast.ref.boost__beast__http__read `read`], [link "
"beast.ref.boost__beast__http__read_header `read_header`], [link "
"beast.ref.boost__beast__http__read_some `read_some`], [link "
"beast.ref.boost__beast__http__async_read `async_read`], [link "
"beast.ref.boost__beast__http__async_read_header `async_read_header`], and "
"[link beast.ref.boost__beast__http__async_read_some `async_read_some`] read "
"HTTP/1 message data from a [link beast.concepts.streams stream]."

#. type: variablelist cell
#: 25
#, fuzzy
msgid "Stream Writing"
msgstr "Stream Writing"

#. type: variablelist cell
#: 25
#, fuzzy
msgid ""
"The functions [link beast.ref.boost__beast__http__write `write`], [link "
"beast.ref.boost__beast__http__write_header `write_header`], [link "
"beast.ref.boost__beast__http__write_some `write_some`], [link "
"beast.ref.boost__beast__http__async_write `async_write`], [link "
"beast.ref.boost__beast__http__async_write_header `async_write_header`], and "
"[link beast.ref.boost__beast__http__async_write_some `async_write_some`] "
"write HTTP/1 message data to a [link beast.concepts.streams stream]."
msgstr ""
"The functions [link beast.ref.boost__beast__http__write `write`], [link "
"beast.ref.boost__beast__http__write_header `write_header`], [link "
"beast.ref.boost__beast__http__write_some `write_some`], [link "
"beast.ref.boost__beast__http__async_write `async_write`], [link "
"beast.ref.boost__beast__http__async_write_header `async_write_header`], and "
"[link beast.ref.boost__beast__http__async_write_some `async_write_some`] "
"write HTTP/1 message data to a [link beast.concepts.streams stream]."

#. type: variablelist cell
#: 25
#, fuzzy
msgid "Serialization"
msgstr "Serialization"

#. type: variablelist cell
#: 25
#, fuzzy
msgid ""
"The __serializer__ produces a series of octet buffers conforming to the "
"__rfc7230__ wire representation of a __message__."
msgstr ""
"The __serializer__ produces a series of octet buffers conforming to the "
"__rfc7230__ wire representation of a __message__."

#. type: variablelist cell
#: 25
#, fuzzy
msgid "Parsing"
msgstr "Parsing"

#. type: variablelist cell
#: 25
#, fuzzy
msgid ""
"The __parser__ attempts to convert a series of octet buffers into a "
"__message__."
msgstr ""
"The __parser__ attempts to convert a series of octet buffers into a "
"__message__."

#. type: paragraph
#: 74
#, fuzzy
msgid ""
"Interfaces for operating on HTTP messages are structured into several "
"layers. The highest level provides ease of use, while lower levels provide "
"progressively more control, options, and flexibility. At the lowest level "
"customization points are provided, where user defined types can replace "
"parts of the implementation. The layers are arranged thusly:"
msgstr ""
"Interfaces for operating on HTTP messages are structured into several "
"layers. The highest level provides ease of use, while lower levels provide "
"progressively more control, options, and flexibility. At the lowest level "
"customization points are provided, where user defined types can replace "
"parts of the implementation. The layers are arranged thusly:"

#. type: table cell
#: 80
#, fuzzy
msgid "[*6]"
msgstr "[*6]"

#. type: table cell
#: 80
#, fuzzy
msgid "__message__"
msgstr "__message__"

#. type: table cell
#: 80
#, fuzzy
msgid ""
"At the highest level, these free functions send or receive a complete HTTP "
"message in one call. They are designed for ease of use: [link "
"beast.ref.boost__beast__http__read.overload4 `read`], [link "
"beast.ref.boost__beast__http__write.overload4 `write`], [link "
"beast.ref.boost__beast__http__async_read.overload2 `async_read`], and [link "
"beast.ref.boost__beast__http__async_write.overload2 `async_write`]."
msgstr ""
"At the highest level, these free functions send or receive a complete HTTP "
"message in one call. They are designed for ease of use: [link "
"beast.ref.boost__beast__http__read.overload4 `read`], [link "
"beast.ref.boost__beast__http__write.overload4 `write`], [link "
"beast.ref.boost__beast__http__async_read.overload2 `async_read`], and [link "
"beast.ref.boost__beast__http__async_write.overload2 `async_write`]."

#. type: table cell
#: 80
#, fuzzy
msgid "[*5]"
msgstr "[*5]"

#. type: table cell
#: 80
#, fuzzy
msgid "__parser__, __serializer__"
msgstr "__parser__, __serializer__"

#. type: table cell
#: 80
#, fuzzy
msgid ""
"For more control, callers may take responsibility for managing the required "
"__parser__ or __serializer__ transient state objects. This allows additional "
"configuration such as limiting the number of bytes for message components "
"during parsing, or regulating the size of buffers emitted during output. "
"These functions send or receive complete messages using a serializer or "
"parser: [link beast.ref.boost__beast__http__read.overload2 `read`], [link "
"beast.ref.boost__beast__http__write.overload2 `write`], [link "
"beast.ref.boost__beast__http__async_read.overload1 `async_read`], and [link "
"beast.ref.boost__beast__http__async_write.overload1 `async_write`]."
msgstr ""
"For more control, callers may take responsibility for managing the required "
"__parser__ or __serializer__ transient state objects. This allows additional "
"configuration such as limiting the number of bytes for message components "
"during parsing, or regulating the size of buffers emitted during output. "
"These functions send or receive complete messages using a serializer or "
"parser: [link beast.ref.boost__beast__http__read.overload2 `read`], [link "
"beast.ref.boost__beast__http__write.overload2 `write`], [link "
"beast.ref.boost__beast__http__async_read.overload1 `async_read`], and [link "
"beast.ref.boost__beast__http__async_write.overload1 `async_write`]."

#. type: table cell
#: 80
#, fuzzy
msgid "[*4]"
msgstr "[*4]"

#. type: table cell
#: 80
#, fuzzy
msgid "__header__"
msgstr "__header__"

#. type: table cell
#: 80
#, fuzzy
msgid ""
"Sometimes it is necessary to first send or receive the HTTP header. For "
"example, to read the header and take action before continuing to read the "
"body. These functions use a __parser__ or __serializer__ to read or write "
"the header: [link beast.ref.boost__beast__http__read_header.overload2 "
"`read_header`], [link beast.ref.boost__beast__http__write_header.overload2 "
"`write_header`], [link beast.ref.boost__beast__http__async_read_header "
"`async_read_header`], and [link "
"beast.ref.boost__beast__http__async_write_header `async_write_header`]."
msgstr ""
"Sometimes it is necessary to first send or receive the HTTP header. For "
"example, to read the header and take action before continuing to read the "
"body. These functions use a __parser__ or __serializer__ to read or write "
"the header: [link beast.ref.boost__beast__http__read_header.overload2 "
"`read_header`], [link beast.ref.boost__beast__http__write_header.overload2 "
"`write_header`], [link beast.ref.boost__beast__http__async_read_header "
"`async_read_header`], and [link "
"beast.ref.boost__beast__http__async_write_header `async_write_header`]."

#. type: table cell
#: 80
#, fuzzy
msgid "[*3]"
msgstr "[*3]"

#. type: table cell
#: 80
#, fuzzy
msgid "partial __message__"
msgstr "partial __message__"

#. type: table cell
#: 80
#, fuzzy
msgid ""
"All of the stream operations at higher levels thus far have operated on a "
"complete header or message. At this level it is possible to send and receive "
"messages incrementally. This allows resource constrained implementations to "
"perform work bounded on storage, or allows better control when setting "
"timeouts for example. These functions read or write bounded amounts of data "
"and return the number of bytes transacted: [link "
"beast.ref.boost__beast__http__read_some.overload2 `read_some`], [link "
"beast.ref.boost__beast__http__write_some.overload2 `write_some`], [link "
"beast.ref.boost__beast__http__async_read_some `async_read_some`], and [link "
"beast.ref.boost__beast__http__async_write_some `async_write_some`]."
msgstr ""
"All of the stream operations at higher levels thus far have operated on a "
"complete header or message. At this level it is possible to send and receive "
"messages incrementally. This allows resource constrained implementations to "
"perform work bounded on storage, or allows better control when setting "
"timeouts for example. These functions read or write bounded amounts of data "
"and return the number of bytes transacted: [link "
"beast.ref.boost__beast__http__read_some.overload2 `read_some`], [link "
"beast.ref.boost__beast__http__write_some.overload2 `write_some`], [link "
"beast.ref.boost__beast__http__async_read_some `async_read_some`], and [link "
"beast.ref.boost__beast__http__async_write_some `async_write_some`]."

#. type: table cell
#: 80
#, fuzzy
msgid "[*2]"
msgstr "[*2]"

#. type: table cell
#: 80
#, fuzzy
msgid "[@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked-body]]"
msgstr "[@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked-body]]"

#. type: table cell
#: 80
#, fuzzy
msgid ""
"Until now parse and serialize operations apply or remove the chunked "
"transfer coding as needed for message payloads whose size is not known ahead "
"of time. For some domain specific niches, it is necessary to assume direct "
"control over incoming or outgoing chunks in a chunk encoded message payload. "
"For parsing this is achieved by setting hooks using the functions [link "
"beast.ref.boost__beast__http__parser.on_chunk_header `on_chunk_header`] and/"
"or [link beast.ref.boost__beast__http__parser.on_chunk_body "
"`on_chunk_body`]. For serializing callers may first emit the header, and "
"then use these buffer sequence adapters to control the contents of each "
"chunk including [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk "
"extensions]] and the [@https://tools.ietf.org/html/rfc7230#section-4.1.2 "
"['trailer-part]]: [link beast.ref.boost__beast__http__chunk_body "
"`chunk_body`], [link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`], "
"[link beast.ref.boost__beast__http__chunk_header `chunk_header`], and [link "
"beast.ref.boost__beast__http__chunk_last `chunk_last`]."
msgstr ""
"Until now parse and serialize operations apply or remove the chunked "
"transfer coding as needed for message payloads whose size is not known ahead "
"of time. For some domain specific niches, it is necessary to assume direct "
"control over incoming or outgoing chunks in a chunk encoded message payload. "
"For parsing this is achieved by setting hooks using the functions [link "
"beast.ref.boost__beast__http__parser.on_chunk_header `on_chunk_header`] and/"
"or [link beast.ref.boost__beast__http__parser.on_chunk_body "
"`on_chunk_body`]. For serializing callers may first emit the header, and "
"then use these buffer sequence adapters to control the contents of each "
"chunk including [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk "
"extensions]] and the [@https://tools.ietf.org/html/rfc7230#section-4.1.2 "
"['trailer-part]]: [link beast.ref.boost__beast__http__chunk_body "
"`chunk_body`], [link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`], "
"[link beast.ref.boost__beast__http__chunk_header `chunk_header`], and [link "
"beast.ref.boost__beast__http__chunk_last `chunk_last`]."

#. type: table cell
#: 80
#, fuzzy
msgid "[*1]"
msgstr "[*1]"

#. type: table cell
#: 80
#, fuzzy
msgid "buffers"
msgstr "buffers"

#. type: table cell
#: 80
#, fuzzy
msgid ""
"For ultimate control, the use of library stream algorithms may be bypassed "
"entirely and instead work directly with buffers by calling members of "
"__parser__ or __serializer__."
msgstr ""
"For ultimate control, the use of library stream algorithms may be bypassed "
"entirely and instead work directly with buffers by calling members of "
"__parser__ or __serializer__."

#. type: table cell
#: 80
#, fuzzy
msgid "[*0]"
msgstr "[*0]"

#. type: table cell
#: 80
#, fuzzy
msgid "['user-defined]"
msgstr "['user-defined]"

#. type: table cell
#: 80
#, fuzzy
msgid ""
"In addition to the typical customization points of __Stream__ and "
"__DynamicBuffer__, user-defined types may replace parts of the library "
"implementation at the lowest level. The customization points include "
"__Fields__ for creating a container to store HTTP fields, __Body__ for "
"defining containers and algorithms used for HTTP message payloads, and user-"
"defined subclasses of __basic_parser__ for implementing custom message "
"representation strategies."
msgstr ""
"In addition to the typical customization points of __Stream__ and "
"__DynamicBuffer__, user-defined types may replace parts of the library "
"implementation at the lowest level. The customization points include "
"__Fields__ for creating a container to store HTTP fields, __Body__ for "
"defining containers and algorithms used for HTTP message payloads, and user-"
"defined subclasses of __basic_parser__ for implementing custom message "
"representation strategies."

#. type: paragraph
#: 193
#, fuzzy
msgid "This documentation assumes some familiarity with __Asio__ and"
msgstr "This documentation assumes some familiarity with __Asio__ and"
