Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolshttp/en/?format=api",
    "source": [
        "The third and widely adopted solution are HTTP cookies. HTTP cookies were initially developed as a private extension by Netscape_. They are now part of the standard :rfc:`6265`. In a nutshell, a cookie is a short string that is chosen by a server to represent a given client. Two HTTP headers are used : `Cookie:` and `Set-Cookie:`. When a server receives an HTTP request from a new client (i.e. an HTTP request that does not contain the `Cookie:` header), it generates a cookie for the client and includes it in the `Set-Cookie:` header of the returned HTTP response. The `Set-Cookie:` header contains several additional parameters including the domain names for which the cookie is valid. The client stores all received cookies on disk and every time it sends an HTTP request, it verifies whether it already knows a cookie for this domain. If so, it attaches the `Cookie:` header to the HTTP request. This is illustrated in the figure below with HTTP 1.1, but cookies also work with HTTP 1.0."
    ],
    "previous_source": "",
    "target": [
        "The third and widely adopted solution are HTTP cookies. HTTP cookies were initially developed as a private extension by Netscape_. They are now part of the standard :rfc:`6265`. In a nutshell, a cookie is a short string that is chosen by a server to represent a given client. Two HTTP headers are used : `Cookie:` and `Set-Cookie:`. When a server receives an HTTP request from a new client (i.e. an HTTP request that does not contain the `Cookie:` header), it generates a cookie for the client and includes it in the `Set-Cookie:` header of the returned HTTP response. The `Set-Cookie:` header contains several additional parameters including the domain names for which the cookie is valid. The client stores all received cookies on disk and every time it sends an HTTP request, it verifies whether it already knows a cookie for this domain. If so, it attaches the `Cookie:` header to the HTTP request. This is illustrated in the figure below with HTTP 1.1, but cookies also work with HTTP 1.0."
    ],
    "id_hash": -7056718366808486058,
    "content_hash": -7056718366808486058,
    "location": "../../protocols/http.rst:391",
    "context": "",
    "note": "",
    "flags": "",
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 76,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 170,
    "source_unit": "https://weblate.info.ucl.ac.be/api/units/36424/?format=api",
    "priority": 100,
    "id": 36424,
    "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolshttp/en/?checksum=1e1180089267cf56",
    "url": "https://weblate.info.ucl.ac.be/api/units/36424/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2021-08-27T15:53:38.628178+02:00"
}