Methods / L7 / HTTP-QUIC
L7 · ApplicationLayer 7HTTP/3QUICProxied
HTTP-QUIC stress test
An HTTP/3 over QUIC request flood that stresses the newest transport path so you can confirm UDP-based edge protections keep pace.
How it works
This method negotiates HTTP/3 over QUIC and drives requests over that UDP-based transport, distributed across a proxy pool. Because QUIC moves the connection and encryption handshake into UDP, it exercises a defense path that many setups protect less thoroughly than TCP-based HTTP. Run it to confirm your edge enforces the same challenge, scoring, and rate-limiting logic on HTTP/3 that it does on HTTP/2, with no gap an attacker could route around.
Parameters
rate125k rq/sRequests per second per worker over QUIC.
threads1-16Worker threads negotiating QUIC connections in parallel.
crawl_depthoff / shallow / deepHow aggressively to discover and target real site URLs.
duration30s-30mLength of the sustained test window.
Run it from the CLI
retro-cli
$ retro run http-quic --target https://example.com --rps 800 --duration 120
HTTP-QUIC FAQ
Why test HTTP/3 separately from HTTP/2?+
QUIC runs over UDP and uses a different handshake, so edge defenses sometimes inspect or rate-limit it less strictly. Testing it directly reveals any protection gap between transports.