What is HTTP/2?
Turkish: HTTP/2
HTTP/2 speeds up web pages and API responses by using multiple streams and compressed headers over a single connection.
What Is HTTP/2?
HTTP/2 keeps the same HTTP request-response semantics but transports them more efficiently. With HTTP/1.1, browsers often opened several connections for many page assets. HTTP/2 can carry multiple streams over one TCP connection at the same time.
This is called multiplexing. If a CSS response is delayed, image or JavaScript responses can continue flowing through the same connection. HTTP/2 also uses HPACK header compression, which reduces repeated bytes in requests that carry cookies, authorization headers, and other recurring metadata.
Performance Impact
HTTP/2 reduces connection overhead on asset-heavy pages and limits the blocking that happens when requests wait on one another. Some HTTP/1.1-era workarounds, such as CSS sprites, domain sharding, or very aggressive file bundling, may therefore offer less benefit than they once did.
Operational Notes
Most browsers use HTTP/2 in practice over HTTPS, so server, CDN, and load balancer support should be checked together. The protocol does not change HTTP methods or status codes. It improves transport efficiency, while API design, cache headers, and security controls still need separate attention.
Related Terms
HTTP is the core web communication protocol that defines request-response exchanges between browsers, API clients, and servers.
HTTP/3HTTP/3 runs HTTP semantics over QUIC and UDP, reducing connection setup time and limiting the impact of packet loss.
HTTPS (HTTP Secure)HTTPS encrypts HTTP traffic with TLS, providing confidentiality, integrity, and server identity between user, browser, and server.