Connection Migration in HTTP/3
You'll learn how HTTP/3 keeps your connection alive when you switch networks, like moving from Wi-Fi to cellular data.
The Problem with Earlier Protocols
In HTTP/1.1 and HTTP/2, connections are identified by a four-tuple: your IP address, your port, the server's IP address, and the server's port. When you switch networks—say, walking out of a coffee shop and losing Wi-Fi—your device gets a new IP address. The old connection dies, and you have to start over with a new handshake. This interrupts downloads, streams, and active requests.
How HTTP/3 Solves This
HTTP/3, built on the QUIC protocol you learned about earlier, uses connection IDs instead of IP addresses to identify connections. Think of it like a loyalty card number at a store: even if you move to a different register (network), the store still knows who you are.
When your device switches from Wi-Fi to cellular:
- Your IP address changes
- HTTP/3 keeps using the same connection ID
- The client sends packets to the server with the old connection ID but from the new IP
- The server recognizes the connection ID and continues the conversation seamlessly
- No reconnection, no handshake delay, no interrupted transfers
Real-World Impact
This is especially valuable for mobile users who frequently transition between networks. A video call doesn't drop when you leave home. A file upload continues when you switch from cellular to office Wi-Fi. The user experience remains smooth without visible interruptions.
Key Takeaway: HTTP/3's connection migration uses persistent connection IDs rather than IP addresses, allowing connections to survive network changes without reconnecting—a major improvement for mobile web performance.