<?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="65b45512e48916ea" weblate-flags="read-only">
        <source>Protocol Primer</source>
        <target state="translated">Protocol Primer</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="c1ac0dcba3801da9" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</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="61361701bbadd36e" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">19</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="119a406246fb60a0" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">29</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1c5818b8eb1ef2f7" weblate-flags="read-only">
        <source>Requests</source>
        <target state="translated">Requests</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">35</context>
        </context-group>
        <note from="developer">type: heading</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="692af3a046cca562" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">37</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="be23f2de0dbfdc4f" weblate-flags="read-only">
        <source>GET / HTTP/1.1\r\n
User-Agent: Beast\r\n
\r\n</source>
        <target state="translated">GET / HTTP/1.1\r\n
User-Agent: Beast\r\n
\r\n</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">47</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b6989e75b52ede39" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">47</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8e93854d945d73f5" weblate-flags="read-only">
        <source>Responses</source>
        <target state="translated">Responses</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">62</context>
        </context-group>
        <note from="developer">type: heading</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="96de2c74e30652b1" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">64</context>
        </context-group>
        <note from="developer">type: paragraph</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">75</context>
        </context-group>
        <note from="developer">type: table code</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="73a96bbb725b7045" weblate-flags="read-only">
        <source>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!".</source>
        <target state="translated">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!".</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">75</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1fbf8e13ddf425b1" weblate-flags="read-only">
        <source>Body</source>
        <target state="translated">Body</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">94</context>
        </context-group>
        <note from="developer">type: heading</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d0c6d56085db7eb9" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">96</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="103" weblate-flags="read-only">
        <source>Special Fields</source>
        <target state="translated">Special Fields</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">103</context>
        </context-group>
        <note from="developer">type: heading</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ff595a05f7edad33" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">105</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="110" weblate-flags="read-only">
        <source>Special Fields</source>
        <target state="translated">Special Fields</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table title</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="b85ab02def1a093f" weblate-flags="read-only">
        <source>Field</source>
        <target state="translated">Field</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f7f5c115cf553484" weblate-flags="read-only">
        <source>Description</source>
        <target state="translated">Description</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="8e1e2c0c1f254d63" weblate-flags="read-only">
        <source>[@https://tools.ietf.org/html/rfc7230#section-6.1 [*`Connection`]]

[@https://tools.ietf.org/html/rfc7230#appendix-A.1.2 [*`Proxy-Connection`]]</source>
        <target state="translated">[@https://tools.ietf.org/html/rfc7230#section-6.1 [*`Connection`]]

[@https://tools.ietf.org/html/rfc7230#appendix-A.1.2 [*`Proxy-Connection`]]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="a6aa16be3aba8a66" weblate-flags="read-only">
        <source>This field allows the sender to indicate desired control options for the current connection. Common values include "close", "keep-alive", and "upgrade".</source>
        <target state="translated">This field allows the sender to indicate desired control options for the current connection. Common values include "close", "keep-alive", and "upgrade".</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d1cec0f7530c4745" weblate-flags="read-only">
        <source>[@https://tools.ietf.org/html/rfc7230#section-3.3.2 [*`Content-Length`]]</source>
        <target state="translated">[@https://tools.ietf.org/html/rfc7230#section-3.3.2 [*`Content-Length`]]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5fa9da1f70c9b583" weblate-flags="read-only">
        <source>When present, this field informs the recipient about the exact size in bytes of the body which follows the message header.</source>
        <target state="translated">When present, this field informs the recipient about the exact size in bytes of the body which follows the message header.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7c7bff0f5e0b5bf5" weblate-flags="read-only">
        <source>[@https://tools.ietf.org/html/rfc7230#section-3.3.1 [*`Transfer-Encoding`]]</source>
        <target state="translated">[@https://tools.ietf.org/html/rfc7230#section-3.3.1 [*`Transfer-Encoding`]]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d87a6ef45e11cf67" weblate-flags="read-only">
        <source>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.

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.</source>
        <target state="translated">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.

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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="0da459e3f566a594" weblate-flags="read-only">
        <source>[@https://tools.ietf.org/html/rfc7230#section-6.7 [*`Upgrade`]]</source>
        <target state="translated">[@https://tools.ietf.org/html/rfc7230#section-6.7 [*`Upgrade`]]</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1b0d5e3956436164" weblate-flags="read-only">
        <source>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.</source>
        <target state="translated">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.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">110</context>
        </context-group>
        <note from="developer">type: table cell</note>
      </trans-unit>
    </body>
  </file>
</xliff>
