Changes

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

{
    "count": 4,
    "next": null,
    "previous": null,
    "results": [
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37563/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/protocolshttp2/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolshttp2/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:31.134650+02:00",
            "action": 59,
            "target": "Two directions have been explored to improve the delivery of these web pages. The first direction is to tune the HTTP protocol. The second approach is to change the entire network stack. We will discuss this approach after having covered the entire stack.",
            "id": 14804,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/14804/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37564/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/protocolshttp2/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolshttp2/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:31.134710+02:00",
            "action": 59,
            "target": "One of the limitations of HTTP from a performance viewpoint is that the requests that are sent by a browser must be sequential. Typically, a browser requests the HTML page. Once the page has been retrieved, the browser parses it to identify all the objects that it references and requests them one after each other. The web page can only be displayed to the user once all the required web objects have been retrieved. This implies that the browser must wait until the reception of each response before sending the next request. Another possibility is to allow the browser to send multiple requests without waiting for their corresponding responses. This approach is called `pipelining` in :rfc:`7230`.",
            "id": 14805,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/14805/?format=api"
        },
        {
            "unit": "https://weblate.info.ucl.ac.be/api/units/37565/?format=api",
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/protocolshttp2/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolshttp2/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:31.134769+02:00",
            "action": 59,
            "target": "HTTP/2.0 is a new version of the HTTP protocol that still uses port 80. When a client contacts an HTTP server, it must be able to determine whether it supports HTTP/1.x or HTTP/2.0. If the client sends a binary encoded HTTP/2.0 request to a server that only supports the ASCII encoded HTTP/1.x, it could cause problems on the server and even crash it. To minimize the risk of crashing HTTP/1.x servers, an HTTP/2.0 session starts like an HTTP/1.1 session and the first request contains the `Connection`, `Upgrade` and `HTTP2-Settings` headers. An example of such a request to upgrade the version of HTTP is shown below.",
            "id": 14806,
            "action_name": "String updated in the repository",
            "url": "https://weblate.info.ucl.ac.be/api/changes/14806/?format=api"
        },
        {
            "unit": null,
            "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/protocolshttp2/?format=api",
            "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolshttp2/en/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-17T01:14:31.134812+02:00",
            "action": 0,
            "target": "",
            "id": 14807,
            "action_name": "Resource update",
            "url": "https://weblate.info.ucl.ac.be/api/changes/14807/?format=api"
        }
    ]
}