<?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="c441faa895a121fc" weblate-flags="read-only">
        <source>The HyperText Transfer Protocol</source>
        <target state="translated">The HyperText Transfer Protocol</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">6</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="80d83d0e2d0f5479" weblate-flags="read-only">
        <source>An important difference between HTTP/1.0, HTTP/1.1 and HTTP/2.0 is their utilization of the underlying transport connections. Answer the three questions below to confirm that you understand the difference between these versions of the HTTP protocol.</source>
        <target state="translated">An important difference between HTTP/1.0, HTTP/1.1 and HTTP/2.0 is their utilization of the underlying transport connections. Answer the three questions below to confirm that you understand the difference between these versions of the HTTP protocol.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">8</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="895ad6881199aefb" weblate-flags="read-only">
        <source>System administrators who are responsible for web servers often want to monitor these servers and check that they are running correctly. As a HTTP server uses TCP on port 80, the simplest solution is to open a TCP connection on port 80 and check that the TCP connection is accepted by the remote host. However, as HTTP/1.x is an ASCII-based protocol, it is also very easy to write a small script that downloads a web page on the server and compares its content with the expected one. Use `telnet` or `ncat` to verify that a web server is running on host `www.computer-networking.info` [#fhttp]_.</source>
        <target state="translated">System administrators who are responsible for web servers often want to monitor these servers and check that they are running correctly. As a HTTP server uses TCP on port 80, the simplest solution is to open a TCP connection on port 80 and check that the TCP connection is accepted by the remote host. However, as HTTP/1.x is an ASCII-based protocol, it is also very easy to write a small script that downloads a web page on the server and compares its content with the expected one. Use `telnet` or `ncat` to verify that a web server is running on host `www.computer-networking.info` [#fhttp]_.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">17</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="f1fc22266fd7648f" weblate-flags="read-only">
        <source>Instead of using `telnet` on port 80, it is also possible to use a command-line tool such as curl_. Use curl_ with the `--trace-ascii tracefile` option to store in `tracefile` all the information exchanged by curl_ when accessing the server.</source>
        <target state="translated">Instead of using `telnet` on port 80, it is also possible to use a command-line tool such as curl_. Use curl_ with the `--trace-ascii tracefile` option to store in `tracefile` all the information exchanged by curl_ when accessing the server.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">19</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="68735633de6094e6" weblate-flags="read-only">
        <source>What is the version of HTTP used by your version of curl_ ?</source>
        <target state="translated">What is the version of HTTP used by your version of curl_ ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">21</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7f838cb81ea9857f" weblate-flags="read-only">
        <source>Can you explain the different headers placed by curl_ in the request ?</source>
        <target state="translated">Can you explain the different headers placed by curl_ in the request ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">22</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5c4725a0a4b3967f" weblate-flags="read-only">
        <source>Can you explain the different headers found in the response ?</source>
        <target state="translated">Can you explain the different headers found in the response ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">23</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2c4c5056822af6e0" weblate-flags="read-only">
        <source>HTTP 1.1, specified in :rfc:`2616`, forces the client to include the `Host:` header in all its requests. HTTP 1.0 does not define the `Host:` header, but most implementations support it. By using `telnet` and `curl` retrieve the first page of the https://www.computer-networking.info web server [#fhttps]_ by sending http requests with and without the `Host:` header. Explain the difference between the two.</source>
        <target state="translated">HTTP 1.1, specified in :rfc:`2616`, forces the client to include the `Host:` header in all its requests. HTTP 1.0 does not define the `Host:` header, but most implementations support it. By using `telnet` and `curl` retrieve the first page of the https://www.computer-networking.info web server [#fhttps]_ by sending http requests with and without the `Host:` header. Explain the difference between the two.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">25</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ddd2202ec463e216" weblate-flags="read-only">
        <source>The headers sent in a HTTP request allow the client to provide additional information to the server. One of these headers is the `Accept-Language` header that allows indicating the preferred language of the client [#flang]_. For example, `curl -HAccept-Language:en http://www.google.be` will send to `http://www.google.be` a HTTP request indicating English (`en`) as the preferred language. Does google provides a different page in French (`fr`) and Walloon (`wa`) ? Same question for `http://www.uclouvain.be` (given the size of the homepage, use ``diff`` to compare the different pages retrieved from `www.uclouvain.be`).</source>
        <target state="translated">The headers sent in a HTTP request allow the client to provide additional information to the server. One of these headers is the `Accept-Language` header that allows indicating the preferred language of the client [#flang]_. For example, `curl -HAccept-Language:en http://www.google.be` will send to `http://www.google.be` a HTTP request indicating English (`en`) as the preferred language. Does google provides a different page in French (`fr`) and Walloon (`wa`) ? Same question for `http://www.uclouvain.be` (given the size of the homepage, use ``diff`` to compare the different pages retrieved from `www.uclouvain.be`).</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">27</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="bb0c35d75deb0768" weblate-flags="read-only">
        <source>Compare the size of the http://www.yahoo.com and http://www.google.com web pages by downloading them with curl_.</source>
        <target state="translated">Compare the size of the http://www.yahoo.com and http://www.google.com web pages by downloading them with curl_.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">29</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="aa931ec7e03ca187" weblate-flags="read-only">
        <source>The `ipvfoo &lt;https://code.google.com/p/ipvfoo/&gt;`_ extension on google chrome allows the user to visually detect whether a website is using IPv6 and IPv4, but also to see which web sites have been contacted when rendering a given web page. Some websites are distributed over several dozens of different servers. Can you find one ?</source>
        <target state="translated">The `ipvfoo &lt;https://code.google.com/p/ipvfoo/&gt;`_ extension on google chrome allows the user to visually detect whether a website is using IPv6 and IPv4, but also to see which web sites have been contacted when rendering a given web page. Some websites are distributed over several dozens of different servers. Can you find one ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">31</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="7007c1a5284aa99e" weblate-flags="read-only">
        <source>Some websites are reachable over both IPv4 and IPv6 while others are only reachable over IPv4 [#fv6only]_. You can use the `-6` (resp. `-4`) option to force curl_ to only use IPv6 (resp. IPv4). Verify that `www.computer-networking.info` is reachable over IPv6 and IPv4 and then check whether your university website already supports IPv6.</source>
        <target state="translated">Some websites are reachable over both IPv4 and IPv6 while others are only reachable over IPv4 [#fv6only]_. You can use the `-6` (resp. `-4`) option to force curl_ to only use IPv6 (resp. IPv4). Verify that `www.computer-networking.info` is reachable over IPv6 and IPv4 and then check whether your university website already supports IPv6.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">33</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2f9153dda886a6a1" weblate-flags="read-only">
        <source>curl_ supports a huge number of options and parameters that are described in its `man page &lt;https://curl.haxx.se/docs/manpage.html&gt;`_ Some of them allow you to force the utilization of a specific version of HTTP. These include `--http0.9`, `--http1.0`, `--http1.1` and `--http2`. Using the latter, verify whether your favorite website supports HTTP/2.0.</source>
        <target state="translated">curl_ supports a huge number of options and parameters that are described in its `man page &lt;https://curl.haxx.se/docs/manpage.html&gt;`_ Some of them allow you to force the utilization of a specific version of HTTP. These include `--http0.9`, `--http1.0`, `--http1.1` and `--http2`. Using the latter, verify whether your favorite website supports HTTP/2.0.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">35</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="108e9e9285ebf0e4" weblate-flags="read-only">
        <source>As for the DNS, besides using software tools that implement the HTTP protocols, it can also be useful to analyze packet traces with wireshark_ . The exercises below contain simple packet traces collected with different versions of the HTTP protocol.</source>
        <target state="translated">As for the DNS, besides using software tools that implement the HTTP protocols, it can also be useful to analyze packet traces with wireshark_ . The exercises below contain simple packet traces collected with different versions of the HTTP protocol.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">37</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c463aea6549199a2" weblate-flags="read-only">
        <source>Footnotes</source>
        <target state="translated">Footnotes</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">50</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="1d7964502b9cc5ce" weblate-flags="read-only">
        <source>The minimum command sent to a HTTP server is `GET / HTTP/1.0` followed by CRLF and a blank line.</source>
        <target state="translated">The minimum command sent to a HTTP server is `GET / HTTP/1.0` followed by CRLF and a blank line.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">51</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="14b6be8db34ce799" weblate-flags="read-only">
        <source>This syllabus is now hosted on a web server using HTTPS (port 443) instead of HTTP (port 80).</source>
        <target state="translated">This syllabus is now hosted on a web server using HTTPS (port 443) instead of HTTP (port 80).</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">53</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ca58a44c1a0fdbc5" weblate-flags="read-only">
        <source>The list of available language tags can be found at http://www.iana.org/assignments/language-subtag-registry. Versions in other formats are available at http://www.langtag.net/registries.html. Additional information about the support of multiple languages in Internet protocols may be found in rfc5646_.</source>
        <target state="translated">The list of available language tags can be found at http://www.iana.org/assignments/language-subtag-registry. Versions in other formats are available at http://www.langtag.net/registries.html. Additional information about the support of multiple languages in Internet protocols may be found in rfc5646_.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">55</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9bc272680604c8a7" weblate-flags="read-only">
        <source>There are probably very few websites that only support IPv6 and not IPv4. If you find one, let us know by submitting a pull-request to change this exercise.</source>
        <target state="translated">There are probably very few websites that only support IPv6 and not IPv4. If you find one, let us know by submitting a pull-request to change this exercise.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/http.rst</context>
          <context context-type="linenumber">57</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
