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-06 20:35+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: Chinese (Simplified Han script) \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 "Protocol Primer" msgstr "Protocol Primer" #. type: paragraph #: 12 #, fuzzy msgid "" "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." msgstr "" "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." #. type: paragraph #: 19 #, fuzzy msgid "" "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." msgstr "" "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." #. type: paragraph #: 29 #, fuzzy msgid "" "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." msgstr "" "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." #. type: heading #: 35 #, fuzzy msgid "Requests" msgstr "Requests" #. type: paragraph #: 37 #, fuzzy msgid "" "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." msgstr "" "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." #. type: table code #: 47 #, fuzzy msgid "" "GET / HTTP/1.1\\r\\n\n" "User-Agent: Beast\\r\\n\n" "\\r\\n" msgstr "" "GET / HTTP/1.1\\r\\n\n" "User-Agent: Beast\\r\\n\n" "\\r\\n" #. type: table cell #: 47 #, fuzzy msgid "" "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." msgstr "" "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." #. type: heading #: 62 #, fuzzy msgid "Responses" msgstr "Responses" #. type: paragraph #: 64 #, fuzzy msgid "" "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." msgstr "" "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." #. type: table code #: 75 #, fuzzy msgid "" "HTTP/1.1 200 OK\\r\\n\n" "Server: Beast\\r\\n\n" "Content-Length: 13\\r\\n\n" "\\r\\n\n" "Hello, world!" msgstr "" "HTTP/1.1 200 OK\\r\\n\n" "Server: Beast\\r\\n\n" "Content-Length: 13\\r\\n\n" "\\r\\n\n" "Hello, world!" #. type: table cell #: 75 #, fuzzy msgid "" "This response has a [@https://tools.ietf.org/html/rfc7231#section-6 200 " "status code] meaning the operation requested completed successfully. The " "obsolete reason phrase is \"OK\". It specifies HTTP version 1.1, and " "contains a body 13 octets in size with the text \"Hello, world!\"." msgstr "" "This response has a [@https://tools.ietf.org/html/rfc7231#section-6 200 " "status code] meaning the operation requested completed successfully. The " "obsolete reason phrase is \"OK\". It specifies HTTP version 1.1, and " "contains a body 13 octets in size with the text \"Hello, world!\"." #. type: heading #: 94 #, fuzzy msgid "Body" msgstr "Body" #. type: paragraph #: 96 #, fuzzy msgid "" "Messages may optionally carry a body. The size of the message body is " "determined by the semantics of the message and the special fields Content-" "Length and Transfer-Encoding. [@https://tools.ietf.org/html/rfc7230#section-" "3.3 rfc7230 section 3.3] provides a comprehensive description for how the " "body length is determined." msgstr "" "Messages may optionally carry a body. The size of the message body is " "determined by the semantics of the message and the special fields Content-" "Length and Transfer-Encoding. [@https://tools.ietf.org/html/rfc7230#section-" "3.3 rfc7230 section 3.3] provides a comprehensive description for how the " "body length is determined." #. type: heading #: 103 #, fuzzy msgctxt "103" msgid "Special Fields" msgstr "Special Fields" #. type: paragraph #: 105 #, fuzzy msgid "" "Certain fields appearing in messages are special. The library understands " "these fields when performing serialization and parsing, taking automatic " "action as needed when the fields are parsed in a message and also setting " "the fields if the caller requests it." msgstr "" "Certain fields appearing in messages are special. The library understands " "these fields when performing serialization and parsing, taking automatic " "action as needed when the fields are parsed in a message and also setting " "the fields if the caller requests it." #. type: table title #: 110 #, fuzzy msgctxt "110" msgid "Special Fields" msgstr "Special Fields" #. type: table cell #: 110 #, fuzzy msgid "Field" msgstr "Field" #. type: table cell #: 110 #, fuzzy msgid "Description" msgstr "Description" #. type: table cell #: 110 #, fuzzy msgid "" "[@https://tools.ietf.org/html/rfc7230#section-6.1 [*`Connection`]]\n" "\n" "[@https://tools.ietf.org/html/rfc7230#appendix-A.1.2 [*`Proxy-Connection`]]" msgstr "" "[@https://tools.ietf.org/html/rfc7230#section-6.1 [*`Connection`]]\n" "\n" "[@https://tools.ietf.org/html/rfc7230#appendix-A.1.2 [*`Proxy-Connection`]]" #. type: table cell #: 110 #, fuzzy msgid "" "This field allows the sender to indicate desired control options for the " "current connection. Common values include \"close\", \"keep-alive\", and " "\"upgrade\"." msgstr "" "This field allows the sender to indicate desired control options for the " "current connection. Common values include \"close\", \"keep-alive\", and " "\"upgrade\"." #. type: table cell #: 110 #, fuzzy msgid "" "[@https://tools.ietf.org/html/rfc7230#section-3.3.2 [*`Content-Length`]]" msgstr "" "[@https://tools.ietf.org/html/rfc7230#section-3.3.2 [*`Content-Length`]]" #. type: table cell #: 110 #, fuzzy msgid "" "When present, this field informs the recipient about the exact size in bytes " "of the body which follows the message header." msgstr "" "When present, this field informs the recipient about the exact size in bytes " "of the body which follows the message header." #. type: table cell #: 110 #, fuzzy msgid "" "[@https://tools.ietf.org/html/rfc7230#section-3.3.1 [*`Transfer-Encoding`]]" msgstr "" "[@https://tools.ietf.org/html/rfc7230#section-3.3.1 [*`Transfer-Encoding`]]" #. type: table cell #: 110 #, fuzzy msgid "" "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.\n" "\n" "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." msgstr "" "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.\n" "\n" "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." #. type: table cell #: 110 #, fuzzy msgid "[@https://tools.ietf.org/html/rfc7230#section-6.7 [*`Upgrade`]]" msgstr "[@https://tools.ietf.org/html/rfc7230#section-6.7 [*`Upgrade`]]" #. type: table cell #: 110 #, fuzzy msgid "" "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." msgstr "" "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."