Initiates requests
Remember HTTP/2
Full name: Hypertext Transfer Protocol version 2
Memory aid: Two lets several streams share one connection.
HTTP/2's common TCP transport still has transport-level head-of-line blocking.
Study area: Protocols & logical ports · Batch 6
Relevant study for: CompTIA Network+ N10-009 · Cisco CCNA 200-301 · CompTIA A+ Core 1 220-1201 · CompTIA Security+ SY0-701 · ISC2 CISSP 2024 outline
Practice with exam flashcards →Backend & Runtime / Knowledge library
HTTP/2
Multiplexes binary-framed streams over one TCP connection
Why learn HTTP/2?
It reduces connection overhead and application-layer head-of-line blocking
The problem it solves
It carries concurrent HTTP exchanges more efficiently than HTTP/1.1
Where it came from
HTTP/2 is a networking and web concept that multiplexes binary-framed streams over one TCP connection. Its guarantees and tradeoffs depend on the concrete implementation and operating context.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Define HTTP/2 and distinguish it from a neighboring concept.
- Choose a realistic task where HTTP/2 is appropriate.
- Identify a failure mode caused by misusing HTTP/2.
- Interpret a small design or result involving HTTP/2.
- Explain one tradeoff or limitation of HTTP/2.
Documentation and sources
- MDN Web Technology Glossary (developer.mozilla.org)
Connect the ideas
Explore next
Real World Example
Optimizing Real-Time Dashboard Synchronization
A financial analytics firm providing high-frequency market data dashboards to institutional traders.
The business problem
The existing HTTP/1.1 infrastructure suffers from head-of-line blocking, where a single slow request for historical chart data stalls the delivery of critical, time-sensitive price updates, causing UI lag.
How this topic solves it
Implementing HTTP/2 allows the application to multiplex multiple binary-framed streams over a single persistent TCP connection, ensuring that small, urgent price updates are not queued behind larger, non-urgent data requests.
- Configure the application load balancer to support the HTTP/2 protocol upgrade.
- Enable binary framing at the application server layer to encapsulate data into independent streams.
- Implement stream prioritization logic to ensure price update frames receive higher processing priority.
- Update client-side fetch logic to utilize persistent connections for concurrent stream management.
This diagram illustrates how a single TCP connection carries multiple independent streams.
Single persistent pipe
Price Updates
Historical Data
- Trader Dashboard → Multiplexes → TCP Connection
- TCP Connection → Carries → Stream 1
- TCP Connection → Carries → Stream 2
Expected business outcome
Traders experience smoother dashboard updates with reduced latency jitter, as critical data flows independently of heavy background assets.
Limitations and checks
The primary trade-off is the complexity of debugging binary-framed traffic compared to plain-text HTTP/1.1; developers must use specialized protocol inspection tools to verify stream integrity and identify potential frame-level errors.