Graph
HTTP/2

🌐HTTP/2

NEW

A major HTTP revision that introduces multiplexed streams, header compression, and server push to improve performance over TCP.

DESCRIPTION

HTTP/2 enhances web performance by allowing multiple streams over a single TCP connection, reducing latency and head-of-line blocking. It uses HPACK header compression and supports server push to proactively deliver resources. Widely supported by browsers and servers, HTTP/2 reduces overhead compared to HTTP/1.1. HTTP/3 further evolves transport using QUIC, but HTTP/2 remains prevalent for many deployments.

ALTERNATIVE DEFINITIONS

MDN Web Docs

HTTP/2 is a major revision of the HTTP network protocol used by the World Wide Web, focusing on performance improvements.

Highlights the performance focus of the revision.

Source

IETF

This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP/2.

Defines HTTP/2 formally as an optimized expression of HTTP semantics.

Source

TLS Header Compression Multiplexing Server Push QUIC TCP

COMPETING TERMS

HTTP/1.1 HTTP-3

RELATIONS

KNOWLEDGE AREAS

Software Engineering Infrastructure Platform & Tooling

TARGET AUDIENCE

Software Developer Software Architect Solution Architect DevOps Engineer Cloud Architect Security Architect

EXTERNAL SOURCES

TOP QUESTIONS

What performance benefits does HTTP/2 offer?

Multiplexing, header compression, and server push reduce latency, improve throughput, and streamline resource delivery.

Category: Benefits

How does HTTP/2 differ from HTTP/1.1?

HTTP/2 multiplexes streams over one connection and compresses headers; HTTP/1.1 uses separate connections or pipelining with limitations.

Category: Comparison

Is TLS required for HTTP/2?

While not strictly required, most browsers only support HTTP/2 over TLS for security.

Category: Security

What is HPACK in HTTP/2?

HPACK is the header compression format used by HTTP/2 to reduce overhead.

Category: Concepts

What is server push in HTTP/2?

It allows servers to send resources proactively before the client requests them, potentially improving load times.

Category: Features

What are common HTTP/2 deployment pitfalls?

Misconfigured TLS, overuse of server push, and neglecting prioritization can negate performance gains.

Category: Mistakes

How does HTTP/2 relate to HTTP/3?

HTTP/3 builds on QUIC to address TCP head-of-line blocking; HTTP/2 remains widely used over TCP.

Category: Evolution

Does HTTP/2 improve SEO?

Indirectly, faster pages can help; search rankings primarily consider content and user experience.

Category: SEO

How to monitor HTTP/2 performance?

Use browser dev tools, server metrics, synthetic tests, and APM solutions to analyze streams and latency.

Category: Observability