Skip to content
AITroveRead. Build. Understand.
Reading list
Make this comfortable

HTTP/3 rollout: keep a tested TCP route when UDP fails

Last updated: 1 Oct 20266 min read
tutorial
AdvancedBy AITrove Editorial

HTTP/3 carries HTTP semantics over QUIC on UDP. An edge can advertise an alternative service to capable clients, yet a client network may block UDP or a particular client may not attempt HTTP/3. The advertised protocol, negotiated protocol, and completed user request are separate observations. A safe rollout preserves a working HTTPS path over TCP while validating the new transport.

Operational decision

A receipt portal enables HTTP/3 at the edge. Start with a small cohort and record the alternative-service response, actual protocol selected, handshake failures, and request success by network. Use a client that can force HTTP/3 to verify the new path, then block UDP in an isolated network and test whether that client's normal request succeeds through the existing TCP endpoint within the user latency budget. Repeat after the client has cached the alternative-service advertisement; behavior may differ from a fresh profile. Check that certificate and HTTP routing results are the same on both transports and that rate limits do not give one protocol an unintended advantage. Roll back by stopping new advertisement and keeping the TCP route healthy; cached advertisements may persist until their lifetime expires, so monitor attempted HTTP/3 connections during the drain window.

Output
Receipt edge transport gate
HTTP/3 advertised: only after UDP route passes synthetic check
Observed protocol: log negotiated transport per request
UDP blocked: ordinary client request still succeeds over TCP
Cached advertisement: tested through expiry window
Rollback: stop advertising; retain compatible TCP endpoint

Cost and verification

Running two transports consumes extra edge configuration, UDP capacity, and monitoring work. A faster happy-path handshake is not useful if blocked-network clients wait before fallback. Track time to first successful response, failed QUIC attempts, and completed receipt requests by protocol and client network. The fallback is client-specific and should be demonstrated with the supported clients, not assumed from a successful TCP-only probe.

Common Mistakes

  • Do not count an advertisement as proof that HTTP/3 was negotiated.
  • Do not disable the TCP route while fallback remains part of the contract.
  • Do not ignore cached alternative-service entries during rollback.

Connected lessons

Practice and check

devops
operations
Storage details