Skip to content

Post 12: The Response Arrives: Streaming, Content Negotiation & Compression #53

@honeycoder96

Description

@honeycoder96

Epic: #15
Block: 7 — The Response Arrives
Series order: 12 of 18

Description

The server has responded and bytes are arriving. This post covers what happens in the window between the first byte and the full response — streaming, content type negotiation, and compression.

Key topics

  • Streaming response: how the browser begins parsing HTML before the full file downloads
  • Navigation commit: when the browser switches from the old page to the new one
  • Content-Type and MIME types: how the browser decides what to do with the bytes
  • MIME sniffing: when the browser overrides Content-Type based on the actual content
  • Content-Encoding vs Transfer-Encoding: the difference between compression and chunked delivery
  • Chunked transfer encoding: sending a response in pieces without knowing the total size upfront
  • Compression: gzip vs Brotli — algorithm differences, compression ratios, browser support
  • Accept-Encoding / Content-Encoding negotiation: how browser and server agree on compression

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions