HTTPS
posts (7)
- The Layers of HTTP in the Browser: From fetch() to QUIC7/9
HTTP/2: Multiplexing Changed the Frontend Network Model
The same HTTP semantics, a different wire format. Many parallel requests do not mean many sockets, and stream independence ends at TCP.
- 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…
- Gateway API Without the Magic4/4
Migrating from ingress-nginx to Gateway API
Migrating from ingress-nginx is not mechanical YAML translation. First, separate the application contract from controller-specific behavior.
- Gateway API Without the Magic3/4
GatewayClass: A Contract With the Implementation
GatewayClass is not an environment label. It is where Kubernetes Gateway API meets a specific controller.
- Gateway API Without the Magic2/4
Gateway Does Not Always Mean the Same Thing
The word gateway mixes a product, a network role, and a Kubernetes API. Without that split, it is easy to compare things from different layers.
- Gateway API Without the Magic1/4
From Service to Gateway API: Where the Problem Came From
Ingress did not fail because it was bad. It failed because its small specification had no language for production HTTP behavior.
- series · 4 parts
Gateway API Without the Magic
A short entry point to a series about where Gateway API came from, how it differs from Ingress, and how to approach an ingress-nginx migration.