Boost Beast Translation (zh_Hans)/Doc / Qbk / 04 Http / 02 Message (qbk) — Chinese (Simplified Han script) @ Boost-Weblate: A body whose `value_type` is a [@boost:/libs/core/doc/html/core/span.html `span`], a non-owning …

Zen

Translation

Source string description

type: table cell

English

Chinese (Simplified Han script)

Needs editing (Needs rewriting)

Skip

Loading…

admin

String added in the repository

English

Chinese (Simplified Han script) 200 characters editedCurrent translationState: Needs editing (Needs rewriting)

06/05/2026

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical.

Reset

Glossary

English	Chinese (Simplified Han script)
No related strings found in the glossary.

String information

Source string description

type: table cell

Unit identifier

58150

Source string location

string ID 120

String age

06/05/2026

Last updated

06/05/2026

Source string age

06/05/2026

Translation file QuickBook file

doc/qbk/04_http/02_message_zh_Hans.qbk, string 35

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the previous translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.

Key	English	Chinese (Simplified Han script)
	/// A typical HTTP request header template<class Fields> using request_header = header<true, Fields>;	/// A typical HTTP request header template<class Fields> using request_header = header<true, Fields>;
	[link beast.ref.boost__beast__http__response_header `response_header`]	[link beast.ref.boost__beast__http__response_header `response_header`]
	/// A typical HTTP response header template<class Fields> using response_header = header<false, Fields>;	/// A typical HTTP response header template<class Fields> using response_header = header<false, Fields>;
	Requests and responses share the version, fields, and body but have a few members unique to the type. This is implemented by declaring the header classes as partial specializations of `isRequest`. __message__ is derived from __header__; a message may be passed as an argument to a function taking a suitably typed header as a parameter. Additionally, `header` is publicly derived from `Fields`; a message inherits all the member functions of `Fields`. This diagram shows the inheritance relationship between header and message, along with some of the notable differences in members in each partial specialization:	Requests and responses share the version, fields, and body but have a few members unique to the type. This is implemented by declaring the header classes as partial specializations of `isRequest`. __message__ is derived from __header__; a message may be passed as an argument to a function taking a suitably typed header as a parameter. Additionally, `header` is publicly derived from `Fields`; a message inherits all the member functions of `Fields`. This diagram shows the inheritance relationship between header and message, along with some of the notable differences in members in each partial specialization:
	Body Types	Body Types
	Beast defines the __Body__ concept, which determines both the type of the [link beast.ref.boost__beast__http__message.body `message::body`] member (as seen in the diagram above) and may also include algorithms for transferring buffers in and out. These algorithms are used during parsing and serialization. Users may define their own body types which meet the requirements, or use the ones that come with the library:	Beast defines the __Body__ concept, which determines both the type of the [link beast.ref.boost__beast__http__message.body `message::body`] member (as seen in the diagram above) and may also include algorithms for transferring buffers in and out. These algorithms are used during parsing and serialization. Users may define their own body types which meet the requirements, or use the ones that come with the library:
	[link beast.ref.boost__beast__http__buffer_body `buffer_body`]	[link beast.ref.boost__beast__http__buffer_body `buffer_body`]
	A body whose [link beast.ref.boost__beast__http__buffer_body__value_type `value_type`] holds a raw pointer and size to a caller-provided buffer. This allows for serialization of body data coming from external sources, and incremental parsing of message body content using a fixed size buffer.	A body whose [link beast.ref.boost__beast__http__buffer_body__value_type `value_type`] holds a raw pointer and size to a caller-provided buffer. This allows for serialization of body data coming from external sources, and incremental parsing of message body content using a fixed size buffer.
	[link beast.ref.boost__beast__http__dynamic_body `dynamic_body`] [link beast.ref.boost__beast__http__basic_dynamic_body `basic_dynamic_body`]	[link beast.ref.boost__beast__http__dynamic_body `dynamic_body`] [link beast.ref.boost__beast__http__basic_dynamic_body `basic_dynamic_body`]
	A body whose `value_type` is a __DynamicBuffer__. It inherits the insertion complexity of the underlying choice of dynamic buffer. Messages with this body type may be serialized and parsed.	A body whose `value_type` is a __DynamicBuffer__. It inherits the insertion complexity of the underlying choice of dynamic buffer. Messages with this body type may be serialized and parsed.
	[link beast.ref.boost__beast__http__empty_body `empty_body`]	[link beast.ref.boost__beast__http__empty_body `empty_body`]
	A special body with an empty `value_type` indicating that the message has no body. Messages with this body may be serialized and parsed; however, body octets received while parsing a message with this body will generate a unique error.	A special body with an empty `value_type` indicating that the message has no body. Messages with this body may be serialized and parsed; however, body octets received while parsing a message with this body will generate a unique error.
	[link beast.ref.boost__beast__http__file_body `file_body`] [link beast.ref.boost__beast__http__basic_file_body `basic_file_body`]	[link beast.ref.boost__beast__http__file_body `file_body`] [link beast.ref.boost__beast__http__basic_file_body `basic_file_body`]
	This body is represented by a file opened for either reading or writing. Messages with this body may be serialized and parsed. HTTP algorithms will use the open file for reading and writing, for streaming and incremental sends and receives.	This body is represented by a file opened for either reading or writing. Messages with this body may be serialized and parsed. HTTP algorithms will use the open file for reading and writing, for streaming and incremental sends and receives.
	[link beast.ref.boost__beast__http__span_body `span_body`]	[link beast.ref.boost__beast__http__span_body `span_body`]
	A body whose `value_type` is a [@boost:/libs/core/doc/html/core/span.html `span`], a non-owning reference to a single linear buffer of bytes. Messages with this body type may be serialized and parsed.	A body whose `value_type` is a [@boost:/libs/core/doc/html/core/span.html `span`], a non-owning reference to a single linear buffer of bytes. Messages with this body type may be serialized and parsed.
	[link beast.ref.boost__beast__http__string_body `string_body`] [link beast.ref.boost__beast__http__basic_string_body `basic_string_body`]	[link beast.ref.boost__beast__http__string_body `string_body`] [link beast.ref.boost__beast__http__basic_string_body `basic_string_body`]
	A body whose `value_type` is `std::basic_string` or `std::string`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed. This is the type of body used in the examples.	A body whose `value_type` is `std::basic_string` or `std::string`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed. This is the type of body used in the examples.
	[link beast.ref.boost__beast__http__vector_body `vector_body`]	[link beast.ref.boost__beast__http__vector_body `vector_body`]
	A body whose `value_type` is `std::vector`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed.	A body whose `value_type` is `std::vector`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed.
	Usage	Usage
	These examples show how to create and fill in request and response objects: Here we build an [@https://tools.ietf.org/html/rfc7231#section-4.3.1 HTTP GET] request with an empty message body:	These examples show how to create and fill in request and response objects: Here we build an [@https://tools.ietf.org/html/rfc7231#section-4.3.1 HTTP GET] request with an empty message body:
	Create Request	Create Request
193	Statements	Statements
193	Serialized Result	Serialized Result
	[http_snippet_2]	[http_snippet_2]
	GET /index.htm HTTP/1.1\r\n Accept: text/html\r\n User-Agent: Beast\r\n \r\n	GET /index.htm HTTP/1.1\r\n Accept: text/html\r\n User-Agent: Beast\r\n \r\n
	In this code we create an HTTP response with a status code indicating success. This message has a body with a non-zero length. The function [link beast.ref.boost__beast__http__message.prepare_payload `message::prepare_payload`] automatically sets the Content-Length or Transfer-Encoding field depending on the content and type of the `body` member. Use of this function is optional; these fields may also be set explicitly.	In this code we create an HTTP response with a status code indicating success. This message has a body with a non-zero length. The function [link beast.ref.boost__beast__http__message.prepare_payload `message::prepare_payload`] automatically sets the Content-Length or Transfer-Encoding field depending on the content and type of the `body` member. Use of this function is optional; these fields may also be set explicitly.
	Create Response	Create Response
214	Statements	Statements
214	Serialized Result	Serialized Result

	English	Chinese (Simplified Han script)	Actions
	Message Containers	Message Containers
	__message__	__message__
	/// An HTTP message template< bool isRequest, // `true` for requests, `false` for responses class Body, // Controls the container and algorithms used for the body class Fields = fields> // The type of container to store the fields class message;	/// An HTTP message template< bool isRequest, // `true` for requests, `false` for responses class Body, // Controls the container and algorithms used for the body class Fields = fields> // The type of container to store the fields class message;
	[link beast.ref.boost__beast__http__request `request`]	[link beast.ref.boost__beast__http__request `request`]
	/// A typical HTTP request template<class Body, class Fields = fields> using request = message<true, Body, Fields>;	/// A typical HTTP request template<class Body, class Fields = fields> using request = message<true, Body, Fields>;
	[link beast.ref.boost__beast__http__response `response`]	[link beast.ref.boost__beast__http__response `response`]
	/// A typical HTTP response template<class Body, class Fields = fields> using response = message<false, Body, Fields>;	/// A typical HTTP response template<class Body, class Fields = fields> using response = message<false, Body, Fields>;
	A body whose [link beast.ref.boost__beast__http__buffer_body__value_type `value_type`] holds a raw pointer and size to a caller-provided buffer. This allows for serialization of body data coming from external sources, and incremental parsing of message body content using a fixed size buffer.	A body whose [link beast.ref.boost__beast__http__buffer_body__value_type `value_type`] holds a raw pointer and size to a caller-provided buffer. This allows for serialization of body data coming from external sources, and incremental parsing of message body content using a fixed size buffer.
	[link beast.ref.boost__beast__http__dynamic_body `dynamic_body`] [link beast.ref.boost__beast__http__basic_dynamic_body `basic_dynamic_body`]	[link beast.ref.boost__beast__http__dynamic_body `dynamic_body`] [link beast.ref.boost__beast__http__basic_dynamic_body `basic_dynamic_body`]
	A body whose `value_type` is a __DynamicBuffer__. It inherits the insertion complexity of the underlying choice of dynamic buffer. Messages with this body type may be serialized and parsed.	A body whose `value_type` is a __DynamicBuffer__. It inherits the insertion complexity of the underlying choice of dynamic buffer. Messages with this body type may be serialized and parsed.
	[link beast.ref.boost__beast__http__empty_body `empty_body`]	[link beast.ref.boost__beast__http__empty_body `empty_body`]
	A special body with an empty `value_type` indicating that the message has no body. Messages with this body may be serialized and parsed; however, body octets received while parsing a message with this body will generate a unique error.	A special body with an empty `value_type` indicating that the message has no body. Messages with this body may be serialized and parsed; however, body octets received while parsing a message with this body will generate a unique error.
	[link beast.ref.boost__beast__http__file_body `file_body`] [link beast.ref.boost__beast__http__basic_file_body `basic_file_body`]	[link beast.ref.boost__beast__http__file_body `file_body`] [link beast.ref.boost__beast__http__basic_file_body `basic_file_body`]
	This body is represented by a file opened for either reading or writing. Messages with this body may be serialized and parsed. HTTP algorithms will use the open file for reading and writing, for streaming and incremental sends and receives.	This body is represented by a file opened for either reading or writing. Messages with this body may be serialized and parsed. HTTP algorithms will use the open file for reading and writing, for streaming and incremental sends and receives.
	[link beast.ref.boost__beast__http__span_body `span_body`]	[link beast.ref.boost__beast__http__span_body `span_body`]
	A body whose `value_type` is a [@boost:/libs/core/doc/html/core/span.html `span`], a non-owning reference to a single linear buffer of bytes. Messages with this body type may be serialized and parsed.	A body whose `value_type` is a [@boost:/libs/core/doc/html/core/span.html `span`], a non-owning reference to a single linear buffer of bytes. Messages with this body type may be serialized and parsed.
	[link beast.ref.boost__beast__http__string_body `string_body`] [link beast.ref.boost__beast__http__basic_string_body `basic_string_body`]	[link beast.ref.boost__beast__http__string_body `string_body`] [link beast.ref.boost__beast__http__basic_string_body `basic_string_body`]
	A body whose `value_type` is `std::basic_string` or `std::string`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed. This is the type of body used in the examples.	A body whose `value_type` is `std::basic_string` or `std::string`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed. This is the type of body used in the examples.
	[link beast.ref.boost__beast__http__vector_body `vector_body`]	[link beast.ref.boost__beast__http__vector_body `vector_body`]
	A body whose `value_type` is `std::vector`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed.	A body whose `value_type` is `std::vector`. Insertion complexity is amortized constant time, while capacity grows geometrically. Messages with this body type may be serialized and parsed.
	Usage	Usage
	These examples show how to create and fill in request and response objects: Here we build an [@https://tools.ietf.org/html/rfc7231#section-4.3.1 HTTP GET] request with an empty message body:	These examples show how to create and fill in request and response objects: Here we build an [@https://tools.ietf.org/html/rfc7231#section-4.3.1 HTTP GET] request with an empty message body:
	Create Request	Create Request
	[http_snippet_2]	[http_snippet_2]
	GET /index.htm HTTP/1.1\r\n Accept: text/html\r\n User-Agent: Beast\r\n \r\n	GET /index.htm HTTP/1.1\r\n Accept: text/html\r\n User-Agent: Beast\r\n \r\n
	In this code we create an HTTP response with a status code indicating success. This message has a body with a non-zero length. The function [link beast.ref.boost__beast__http__message.prepare_payload `message::prepare_payload`] automatically sets the Content-Length or Transfer-Encoding field depending on the content and type of the `body` member. Use of this function is optional; these fields may also be set explicitly.	In this code we create an HTTP response with a status code indicating success. This message has a body with a non-zero length. The function [link beast.ref.boost__beast__http__message.prepare_payload `message::prepare_payload`] automatically sets the Content-Length or Transfer-Encoding field depending on the content and type of the `body` member. Use of this function is optional; these fields may also be set explicitly.
	Create Response	Create Response
	[http_snippet_3]	[http_snippet_3]
	HTTP/1.1 200 OK\r\n Server: Beast\r\n Content-Length: 13\r\n \r\n Hello, world!	HTTP/1.1 200 OK\r\n Server: Beast\r\n Content-Length: 13\r\n \r\n Hello, world!
	The implementation will automatically fill in the obsolete [@https://tools.ietf.org/html/rfc7230#section-3.1.2 reason-phrase] from the status code when serializing a message. Or it may be set directly using [link beast.ref.boost__beast__http__header.reason.overload2 `header::reason`].	The implementation will automatically fill in the obsolete [@https://tools.ietf.org/html/rfc7230#section-3.1.2 reason-phrase] from the status code when serializing a message. Or it may be set directly using [link beast.ref.boost__beast__http__header.reason.overload2 `header::reason`].

Translation

Things to check

Unchanged translation

Glossary

String information

Source string description

Details

Unit identifier

Source string location

String age

Last updated

Source string age

Translation file QuickBook file