HTTP/3 is now standardized and shipped in all major browsers (partially enabled in Safari) [1]. Enabling it may help the servers in more efficiently using bandwidth and increase performance.
HAProxy has production-ready support of HTTP/3 as of version 2.8 [2].
One benefit of HTTP/3 is it may be more resistant to censorship, as initial packets of a connection (where SNI lies) are encrypted using well known keys.
Links
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T208242 Investigate using RFC 7838 Alternate Services to better optimize edge connections | |||
| Open | None | T238034 Enable HTTP/3 (QUIC) support on Wikimedia servers |
We should consider QUIC and HTTP/3 adoption carefully as it implies a switch from TCP to UDP, and that could open new (D)DoS vectors and render unusable some mitigation techniques.
@Masumrezarock100 This is something that needs to be done on the operations side of thigs, so i've removed Site-Requests which is for local wiki config changes.
Mozilla now supports HTTP/3 and the editor's draft has reached the final call, RFC should only be a short time away.
The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all tickets that aren't are neither part of our current planned work nor clearly a recent, higher-priority emergent issue. This is simply one step in a larger task cleanup effort. Further triage of these tickets (and especially, organizing future potential project ideas from them into a new medium) will occur afterwards! For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!
By the way, I want to emphasize that QUIC encrypts initial packets of a connection (where SNI lies). Even though its key is known, inspecting it would require more processing power, making QUIC harder to censor.
HTTP/3 will fall back to HTTP/2, so UDP could be disabled any time there's an issue (DDoS attack) with it.
Note that HTTP/3 would be a larger improvement for people in less well-connected countries and people with poorer connections, but also for everyone located further away from the US west coast (see e.g. T348599 for CloudVPS and Toolforge slowness in Europe).