Konrad Kowalski (rootsher)Principal Platform & Reliability Architect011011110110000101000000001011100000001100011001

Fetch API

posts (4)

  1. The Layers of HTTP in the Browser: From fetch() to QUIC1/9

    Request and Response: What Does the Browser Actually Send?

    A request is not a URL, and an HTTP response is not always JSON. Headers and body have separate lifecycles, and an HTTP error is not a network failure.

  2. series · 9 parts

    The Layers of HTTP in the Browser: From fetch() to QUIC

    Two lines of fetch() cover several layers: the browser API, HTTP semantics, the wire protocol and the transport. This series separates them so the Network…

  3. Ways of Talking to a Backend: From HTML Forms to GraphQL3/6

    Fetch API: The Modern Browser Interface to HTTP

    fetch did not change the communication model, only the interface. Request and Response are objects, the body is a stream, and a 404 is not an error.

  4. series · 6 parts

    Ways of Talking to a Backend: From HTML Forms to GraphQL

    The layers of frontend to backend communication from the bottom up: forms, XHR and fetch start the request, HTTP carries it, and REST, RPC and GraphQL model…