Skip to content

Standard

HTTP/3

Third major version of the HTTP protocol, running over QUIC instead of TCP, standardized in RFC 9114 for faster, more reliable web connections.

Known aliases

  • HTTP3
  • HTTP/3 over QUIC
  • RFC 9114

Current stories

securityOne report1 publisher

Turbo Intruder hits 100,000 requests a second from a laptop over HTTP/3

PortSwigger has shipped HTTP/3 support in Turbo Intruder and a Burp Suite adapter, pushing more than three times the request rate it managed over HTTP/1.1 and adding two QUIC race techniques for tighter timing windows.

Publishers:portswigger.net

Reality

Evidence52
Adoption14
Hype gap+20
Incentives78
Confidence58
buildOne report1 publisher

HTTP/2 gives a lossy mobile link one TCP connection to stall instead of six

A dev.to guide walks Laravel apps from HTTP/1.1 to HTTP/3 on nginx, and the part worth reading twice is its admission that the middle step can hurt, because one connection carrying 40 streams stalls on one lost packet.

Publishers:dev.to

Reality

Evidence62
Adoption75
Hype gap+5
Incentives50
Confidence66
buildOne report1 publisher

Quarkus 4 rebuilds its I/O core on Vert.x 5.1.2 and Netty 4.2 for a November GA

Beta 1 arrives in September with breaking changes frozen, leaving about two months of testing before general availability, and Quarkus 3.40 LTS has community maintenance until September 2027 for teams that need longer.

Publishers:dev.to

Reality

Evidence55
Adoption20
Hype gap+15
Incentives45
Confidence55
buildOne report1 publisher

Make HTTP/3 earn its place in your Unity client

Unity 6.5 shipped a protocol pin whose enum tops out at HTTP/2, which tells you where the engine puts the risk. QUIC only pays for concurrent, small-object traffic, and only if your CDN negotiates it.

Publishers:dev.to

Reality

Evidence52
Adoption28
Hype gap−12
Incentives30
Confidence50
buildOne report1 publisher

Your edge speaks HTTP/3, your origin speaks HTTP/1.1: that gap is now a DoS primitive

A new arXiv paper describes two amplification attacks that turn a CDN's HTTP/3 front end into a pump aimed at HTTP/1.1 origins. Two CDN vendors have paid bounties and shipped the authors' mitigations.

Publishers:arxiv.org

Reality

Evidence64
Adoption58
Hype gap+12
Incentives55
Confidence57
securityOne report1 publisher

CDN Tsunami: the protocol translation you pay for is the amplifier

Two disclosed DoS techniques turn HTTP/3-to-HTTP/1.1 conversion at six major CDNs into up to 350x load on the origin, with no configuration change by the customer.

Reality

Evidence66
Adoption34
Hype gap+28
Incentives52
Confidence54