You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HTTP3 QUIC connection migration to another network #3529
When a client connects to haproxy using HTTP3, the QUIC protocol gives you a connection ID that you can re-use on a different IP or even a different network. This is super useful if you're roaming or switching from wifi/LTE. Sadly, Haproxy doesnt support connection handoff, as the current documentation implies:
HTTP/3 is implemented over QUIC, itself implemented over UDP. QUIC solves the
head of line blocking at transport level by means of independently treated
streams. Indeed, when experiencing loss, an impacted stream does not affect the
other streams. QUIC also provides connection migration support but currently
haproxy does not support it.
Expected Behavior
The connection migration happens seamlessly, and the user can reach the resource from a different network. Right now, since this isn't implemented, the connection times out for 30 seconds on browsers like Safari, then falls back to http2 and then back again to http3.
Activity
haproxyFred commentedon Oct 13, 2026
I've started working on this issue, but it's not a easy one to fix.