HTTP/3 or QUIC support?

[nagyrobi]

Any plans to add support for QUIC protocol?

An important difference in HTTP/3 is that it runs on QUIC, a new transport protocol. QUIC is designed to be fast and to support switching rapidly between networks. It relies on the UDP rather than the TCP, which mitigates an issue called head-of-line blocking in TCP, where network packet loss or reordering can slow down high-transaction connections. Furthermore, QUIC separates out the layer 4 transport connection from the layer 3 IP flow, allowing for migration between different networks without disruption.

QUIC can better support mobile-heavy Internet usage in which people carry smartphones and constantly switch from one network to another as they move about their day. This type of Internet usage was not common when the first Internet protocols were developed: devices were less portable and did not switch networks very often.

In 2016 it was adopted by the Internet Engineering Task Force (IETF) — a vendor-neutral standards organization — as they started creating the new HTTP/3 standard. After consulting with experts around the world, the IETF has made a host of changes to develop the now-standard version of QUIC published as RFC 9000.

---

Would be nice to use backends the usual way via TCP, and expose them to the front also via QUIC on UDP ports 80 and 443.

[graygnuorg]

Hi Róbert. Yes, but in somewhat long run. My nearest plans are to add HTTP/2 first.