<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
  <file original="NoName" source-language="en" datatype="plaintext" target-language="en">
    <body>
      <trans-unit xml:space="preserve" approved="no" id="3c914245c25e169b" weblate-flags="read-only">
        <source>Message Containers</source>
        <target state="translated">Message Containers</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">10</context>
        </context-group>
        <note from="developer">type: section title</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="287bfb9742948af2" weblate-flags="read-only">
        <source>Beast provides a single class template __message__ and some aliases which model HTTP/1 and [@https://tools.ietf.org/html/rfc7540 HTTP/2] messages:</source>
        <target state="translated">Beast provides a single class template __message__ and some aliases which model HTTP/1 and [@https://tools.ietf.org/html/rfc7540 HTTP/2] messages:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">12</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f5351ff85ab23173" weblate-flags="read-only">
        <source>Message</source>
        <target state="translated">Message</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table title</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="17" weblate-flags="read-only">
        <source>Name</source>
        <target state="translated">Name</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="17" weblate-flags="read-only">
        <source>Description</source>
        <target state="translated">Description</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0f07a2b73cf789f9" weblate-flags="read-only">
        <source>__message__</source>
        <target state="translated">__message__</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="03dfe3a5e248aaa8" weblate-flags="read-only">
        <source>/// An HTTP message
template&lt;
bool isRequest,             // `true` for requests, `false` for responses
class Body,                 // Controls the container and algorithms used for the body
class Fields = fields&gt;      // The type of container to store the fields
class message;</source>
        <target state="translated">/// An HTTP message
template&lt;
bool isRequest,             // `true` for requests, `false` for responses
class Body,                 // Controls the container and algorithms used for the body
class Fields = fields&gt;      // The type of container to store the fields
class message;</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8f88fa0205dcff0e" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__request `request`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__request `request`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f33cf0fb2dc7adbc" weblate-flags="read-only">
        <source>/// A typical HTTP request
template&lt;class Body, class Fields = fields&gt;
using request = message&lt;true, Body, Fields&gt;;</source>
        <target state="translated">/// A typical HTTP request
template&lt;class Body, class Fields = fields&gt;
using request = message&lt;true, Body, Fields&gt;;</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e17dae9464fd7a0c" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__response `response`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__response `response`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="574173e3f5c4dd9b" weblate-flags="read-only">
        <source>/// A typical HTTP response
template&lt;class Body, class Fields = fields&gt;
using response = message&lt;false, Body, Fields&gt;;</source>
        <target state="translated">/// A typical HTTP response
template&lt;class Body, class Fields = fields&gt;
using response = message&lt;false, Body, Fields&gt;;</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">17</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4edd99e45743654b" weblate-flags="read-only">
        <source>The container offers value semantics including move and copy if supported by __Body__ and __Fields__. User defined template function parameters can accept any message, or can use partial specialization to accept just requests or responses. The default __fields__ is a provided associative container using the standard allocator and supporting modification and inspection of fields. As per __rfc7230__, a non-case-sensitive comparison is used for field names. User defined types for fields are possible. The `Body` type determines the type of the container used to represent the body as well as the algorithms for transferring buffers to and from the container. The library comes with a collection of common body types. As with fields, user defined body types are possible.</source>
        <target state="translated">The container offers value semantics including move and copy if supported by __Body__ and __Fields__. User defined template function parameters can accept any message, or can use partial specialization to accept just requests or responses. The default __fields__ is a provided associative container using the standard allocator and supporting modification and inspection of fields. As per __rfc7230__, a non-case-sensitive comparison is used for field names. User defined types for fields are possible. The `Body` type determines the type of the container used to represent the body as well as the algorithms for transferring buffers to and from the container. The library comes with a collection of common body types. As with fields, user defined body types are possible.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">51</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e224bef651e9308f" weblate-flags="read-only">
        <source>Sometimes it is desired to only work with a header. Beast provides a single class template __header__ and some aliases to model HTTP/1 and HTTP/2 headers:</source>
        <target state="translated">Sometimes it is desired to only work with a header. Beast provides a single class template __header__ and some aliases to model HTTP/1 and HTTP/2 headers:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">63</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0e4b1dfd757ed081" weblate-flags="read-only">
        <source>Header</source>
        <target state="translated">Header</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table title</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="66" weblate-flags="read-only">
        <source>Name</source>
        <target state="translated">Name</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="66" weblate-flags="read-only">
        <source>Description</source>
        <target state="translated">Description</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f0bf2438c5eb8c93" weblate-flags="read-only">
        <source>__header__</source>
        <target state="translated">__header__</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c046c08dfe0cbb86" weblate-flags="read-only">
        <source>/// An HTTP header
template&lt;
bool isRequest,             // `true` for requests, `false` for responses
class Fields = fields&gt;      // The type of container to store the fields
class header;</source>
        <target state="translated">/// An HTTP header
template&lt;
bool isRequest,             // `true` for requests, `false` for responses
class Fields = fields&gt;      // The type of container to store the fields
class header;</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c8f15a92d5ce141f" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__request_header `request_header`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__request_header `request_header`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f009c0bab51b8d2d" weblate-flags="read-only">
        <source>/// A typical HTTP request header
template&lt;class Fields&gt;
using request_header = header&lt;true, Fields&gt;;</source>
        <target state="translated">/// A typical HTTP request header
template&lt;class Fields&gt;
using request_header = header&lt;true, Fields&gt;;</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5263ecbd2b1fa352" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__response_header `response_header`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__response_header `response_header`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0134cc58952ea681" weblate-flags="read-only">
        <source>/// A typical HTTP response header
template&lt;class Fields&gt;
using response_header = header&lt;false, Fields&gt;;</source>
        <target state="translated">/// A typical HTTP response header
template&lt;class Fields&gt;
using response_header = header&lt;false, Fields&gt;;</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">66</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="3f5b9c229ac54e9a" weblate-flags="read-only">
        <source>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:</source>
        <target state="translated">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:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">99</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0634f3181d2f63c7" weblate-flags="read-only">
        <source>Body Types</source>
        <target state="translated">Body Types</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">111</context>
        </context-group>
        <note from="developer">type: heading</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5ce82345296287c2" weblate-flags="read-only">
        <source>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:</source>
        <target state="translated">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:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">113</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d4a1e4aec84fb6b6" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__buffer_body `buffer_body`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__buffer_body `buffer_body`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="cb2067ef84aa9b9f" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="15f028750e1eb199" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__dynamic_body `dynamic_body`]

[link beast.ref.boost__beast__http__basic_dynamic_body `basic_dynamic_body`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__dynamic_body `dynamic_body`]

[link beast.ref.boost__beast__http__basic_dynamic_body `basic_dynamic_body`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f535c943907325c3" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9ffff0c6808171fb" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__empty_body `empty_body`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__empty_body `empty_body`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="672498ceff46fcd6" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="52b1c12ccd0e29b6" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__file_body `file_body`]

[link beast.ref.boost__beast__http__basic_file_body `basic_file_body`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__file_body `file_body`]

[link beast.ref.boost__beast__http__basic_file_body `basic_file_body`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c7f838b0587b16b7" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="443254bff5cb9a8a" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__span_body `span_body`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__span_body `span_body`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="71f33fb0e20c3080" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7ff8db9fe7a57ea5" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__string_body `string_body`]

[link beast.ref.boost__beast__http__basic_string_body `basic_string_body`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__string_body `string_body`]

[link beast.ref.boost__beast__http__basic_string_body `basic_string_body`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="31927d3c32fb36c3" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c8d24699e230ef45" weblate-flags="read-only">
        <source>[link beast.ref.boost__beast__http__vector_body `vector_body`]</source>
        <target state="translated">[link beast.ref.boost__beast__http__vector_body `vector_body`]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="57528d2d0adf90ec" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">120</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="3e765ee54bb93f16" weblate-flags="read-only">
        <source>Usage</source>
        <target state="translated">Usage</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">186</context>
        </context-group>
        <note from="developer">type: heading</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4ef733bf95eac37a" weblate-flags="read-only">
        <source>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:</source>
        <target state="translated">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:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">188</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b8cb208ff47a25e6" weblate-flags="read-only">
        <source>Create Request</source>
        <target state="translated">Create Request</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">193</context>
        </context-group>
        <note from="developer">type: table title</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="193" weblate-flags="read-only">
        <source>Statements</source>
        <target state="translated">Statements</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">193</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="193" weblate-flags="read-only">
        <source>Serialized Result</source>
        <target state="translated">Serialized Result</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">193</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5c57a4e3ab6e267c" weblate-flags="read-only">
        <source>[http_snippet_2]</source>
        <target state="translated">[http_snippet_2]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">193</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4f9448c084995f2f" weblate-flags="read-only">
        <source>GET /index.htm HTTP/1.1\r\n
Accept: text/html\r\n
User-Agent: Beast\r\n
\r\n</source>
        <target state="translated">GET /index.htm HTTP/1.1\r\n
Accept: text/html\r\n
User-Agent: Beast\r\n
\r\n</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">193</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8db2f9dea2e57d92" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">207</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4067091a6feb3309" weblate-flags="read-only">
        <source>Create Response</source>
        <target state="translated">Create Response</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">214</context>
        </context-group>
        <note from="developer">type: table title</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="214" weblate-flags="read-only">
        <source>Statements</source>
        <target state="translated">Statements</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">214</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="214" weblate-flags="read-only">
        <source>Serialized Result</source>
        <target state="translated">Serialized Result</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">214</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="03d33579116be7dc" weblate-flags="read-only">
        <source>[http_snippet_3]</source>
        <target state="translated">[http_snippet_3]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">214</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ba2b7f975a27b176" weblate-flags="read-only">
        <source>HTTP/1.1 200 OK\r\n
Server: Beast\r\n
Content-Length: 13\r\n
\r\n
Hello, world!</source>
        <target state="translated">HTTP/1.1 200 OK\r\n
Server: Beast\r\n
Content-Length: 13\r\n
\r\n
Hello, world!</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">214</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="cb9aa97c7080d954" weblate-flags="read-only">
        <source>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`].</source>
        <target state="translated">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`].</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">229</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
    </body>
  </file>
</xliff>
