HTTP/3
HTTP/3 runs over QUIC (UDP) instead of TCP, eliminating TCP-level head-of-line blocking and offering 0-RTT connections and independent per-stream retransmission.
Purpose
It delivers low-latency HTTP on unreliable networks: 0-RTT resumption and connection migration improve the mobile experience, and independent streams avoid head-of-line blocking.
Mechanism
HTTP/2 semantics map onto QUIC streams: each HTTP/2 stream becomes a QUIC stream, and QUIC provides reliable, ordered per-stream delivery over UDP with integrated TLS 1.3. 0-RTT uses cached TLS session tickets to send data immediately.
Use cases
- Low-latency mobile web
- CDN edge acceleration
- API transport
Related tools
HTTP Status Codes
Reference table of common HTTP status codes (1xx-5xx) with names, categories, and descriptions. Free, private, and 100% client-side. TOOL
URL Parser
Parse a URL into its components: protocol, host, path, query, hash, port, username, and password. Free, private, and 100% client-side. TOOL