Generates telemetry data
Remember HTTP/3
Full name: Hypertext Transfer Protocol version 3
Memory aid: Three takes HTTP onto the QUIC road.
HTTP/3 is not HTTP/2 running over ordinary TCP.
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/3
Carries HTTP semantics over QUIC streams
Why learn HTTP/3?
It improves connection setup and isolates transport loss between streams
The problem it solves
It reduces TCP-level head-of-line blocking for multiplexed HTTP
Where it came from
HTTP/3 is a networking and web concept that carries HTTP semantics over QUIC streams. 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/3 and distinguish it from a neighboring concept.
- Choose a realistic task where HTTP/3 is appropriate.
- Identify a failure mode caused by misusing HTTP/3.
- Interpret a small design or result involving HTTP/3.
- Explain one tradeoff or limitation of HTTP/3.
Documentation and sources
- MDN Web Technology Glossary (developer.mozilla.org)
Connect the ideas
Explore next
Real World Example
Optimizing Satellite-Linked Remote Sensor Data Streams
A remote environmental monitoring firm deploying IoT sensors in regions with high-latency satellite backhaul.
The business problem
Traditional HTTP/2 over TCP suffers from head-of-line blocking where a single packet loss stalls all concurrent streams, causing significant data gaps during intermittent satellite signal interference.
How this topic solves it
HTTP/3 leverages the QUIC transport protocol, which treats each stream independently. If one packet is lost, only the affected stream is delayed, allowing other sensor data streams to continue transmission without interruption.
- Configure the edge gateway to support UDP port 443 for QUIC handshake initiation.
- Enable HTTP/3 support on the load balancer to negotiate the Alt-Svc header.
- Map individual sensor data channels to distinct QUIC streams to isolate transmission errors.
- Implement connection migration logic to maintain sessions when the satellite terminal switches beams.
This diagram illustrates how HTTP/3 decouples data streams over a single QUIC connection.
Single UDP transport layer
Temperature data
Humidity data
- IoT Sensor → multiplexes → QUIC Connection
- QUIC Connection → contains → Stream A
- QUIC Connection → contains → Stream B
Expected business outcome
The system achieves more consistent data ingestion rates despite high packet loss environments, as individual sensor streams no longer block each other during transient network congestion.
Limitations and checks
Increased CPU overhead on the server due to UDP packet processing and QUIC encryption requirements; monitor this by tracking the ratio of CPU utilization to concurrent QUIC connection counts.