Do you know that http/3 allows to go from LTE to WIFI without renegotiating the session. Browser will use same http session.
If you are curious to know about this and other strengths of upcoming http/3 protocol, then this document helps you.
One of the most notable issue is the fact that the single connection of HTTP/2 ends up being a bottleneck for data in a low network quality environment — as network quality degrades, and packets are dropped, the single connection slows the entire process down, and no additional data can be transferred during this time of retransmission.
HTTP/3 implement a new layer protocol called QUIC (Quick UDP Internet Connection). This supports a set of multiplexed connections over UDP and has been designed to provide TLS 1.3 by default by, reducing latency in both connection and data transport.
Connection migration - it allows to transfer networks (for example from LTE to WIFI) without renegotiating the session.
Connection establishment latency reduction
Multiplexing without HOL(head-of-line) blocking
QUIC uses the traditional HTTP ports of 80 and 443
By default, QUIC packets are encrypted.
if QUIC communication does not work between a client and a server, the traffic will fall back to traditional HTTP/HTTPS over TCP
Caveats
Firewall blocks it since it blinds the firewall. Firewall is not able to the content
Safari,
Microsoft Edge,
Mozilla Firefox,
Google Chrome
https://sites.google.com/site/jbsakabffoi12449ujkn/home/networking/http-2
https://images.app.goo.gl/tzcSvkYLmG1MAHeL8
https://medium.com/faun/http-2-spdy-and-http-3-quic-bae7d9a3d484
https://www.fastvue.co/fastvue/blog/googles-quic-protocols-security-and-reporting-implications/
https://images.app.goo.gl/hD2L4K3DDNtpJVD7A
https://en.wikipedia.org/wiki/HTTP/3
https://images.app.goo.gl/uMjVZ5XnQYXe2HkE7
https://images.app.goo.gl/K6rcZXjZdvNPXNAt5
https://dev.to/eesnaola/http-2-vs-http-3-52hi
https://youtu.be/SZEZHou6Rn4?t=248
https://images.app.goo.gl/HPTxLoY9Acjf3Doo6