HTTP/2

The Problems HTTP/2 Solves

HTTPHypertext Transfer Protocol. The application-layer protocol for transmitting web pages, APIs, and other resources. HTTP defines methods (GET, POST, PUT, DELETE) and status codes for client-server communication. 1.1 sends one request per TCP connection at a time (without pipelining). In practice, browsers open 6-8 parallel connections per origin to work around this — wasting resources and adding LatencyThe time delay for a data packet to travel from source to destination, typically measured in milliseconds (ms). Lower latency is critical for real-time applications like video calls, gaming, and financial trading.. HTTP/2 introduces multiplexing: multiple requests and responses flow concurrently over a single SSL/TLSSecure Sockets Layer / Transport Layer Security. Cryptographic protocols that provide encrypted, authenticated communication over a network. SSL is deprecated; modern implementations use TLS 1.2 or TLS 1.3. connection, eliminating head-of-line blocking at the application layer.

Key Features

Header compression (HPACK) reduces repetitive header overhead — significant savings on APIs sending the same Authorization and Content-Type headers with every request. Server push allows the server to proactively send resources (CSS, JS) the client has not yet requested, anticipating its needs. Stream prioritization lets browsers signal which resources are most critical, allowing servers to schedule responses intelligently.

Deployment Considerations

HTTP/2 is negotiated via ALPN during the SSL/TLSSecure Sockets Layer / Transport Layer Security. Cryptographic protocols that provide encrypted, authenticated communication over a network. SSL is deprecated; modern implementations use TLS 1.2 or TLS 1.3. handshake — effectively requiring HTTPSHTTP Secure. The encrypted version of HTTP that uses TLS to protect data in transit between a browser and a web server. Identified by the padlock icon in browsers and the https:// URL scheme. in practice, even though the spec allows cleartext HTTP/2. Most modern Load BalancerA device or service that distributes incoming network traffic across multiple backend servers to ensure no single server is overwhelmed. Improves availability, reliability, and scalability of web applications. and Reverse ProxyA server that sits in front of backend servers, forwarding client requests and returning responses on their behalf. Used for SSL termination, load balancing, caching, and hiding the origin server's identity. solutions (nginx, HAProxy, Cloudflare) support HTTP/2 termination transparently. Because HTTP/2 reuses a single connection, CDNContent Delivery Network. A geographically distributed network of servers that caches and serves content from locations close to end users, reducing latency and improving load times. Major providers include Cloudflare, AWS CloudFront, and Akamai. and proxy layers must be HTTP/2-aware to avoid performance regressions. Despite multiplexing, TCP-level head-of-line blocking remains — a problem that HTTP/3The third major version of HTTP, built on QUIC instead of TCP. HTTP/3 eliminates head-of-line blocking, reduces connection setup latency, and provides built-in encryption, improving performance on unreliable networks. addresses by switching to QUIC. Use HTTP Header Analyzer to verify your server is negotiating HTTP/2 correctly.