« Previous 1 2 3 4
HTTP/1.1 versus HTTP/2 and HTTP/3
Turboboost
Long Path to the Browsers
Servers must do more than understand QUIC, so it follows that the clients also need to support HTTP/3. Because QUIC originates from Google, it is no surprise that Chrome already supports QUIC. Firefox also started offering experimental support in version 72 according to the definition published by the IETF. Microsoft Edge, which is now based on the open source Chromium project, has started the implementation work, which is currently available through Microsoft Edge Insider Canary Channel [6].
Conclusions
Today's standard for delivering web pages and applications is clearly HTTP/2. It solves the most serious problem of HTTP/1.1 – the HTTP head-of-line blocking – which required a client to wait until a request it had made was completed before it could make the next one. This bottleneck in turn caused massive delays, because today's web pages no longer comprise just a handful of files but load a huge volume of additional data. Administrators don't have to go to great lengths to get HTTP/2 up and running. Meanwhile, HTTP/3 is now in the starting blocks and brings with it the change from TCP to QUIC.
Infos
- RFC 2616: https://tools.ietf.org/html/rfc2616
- Host Header as per RFC 7230, section 5.4: https://tools.ietf.org/html/rfc7230#section-5.4
- HTTP/2.0 as per RFC 7540: https://tools.ietf.org/html/rfc7540
- HTTP/2 historical use: https://w3techs.com/technologies/history_overview/site_element/all/y
- Google QUIC draft: https://quicwg.org/base-drafts/draft-ietf-quic-http.html
- Microsoft Edge Insider channel: https://www.microsoftedgeinsider.com/en-us/download
« Previous 1 2 3 4
Buy this article as PDF
(incl. VAT)
Buy ADMIN Magazine
US / Canada
UK / Australia
Related content
-
Quick UDP Internet connections
The UDP-based Quick UDP Internet Connections (QUIC) protocol comes with mandatory TLS encryption and promises faster speeds. -
Setting up HTTP/2 for Nginx
HTTP/2, the current representative of the HTTP family, offers several advantages for website operators and their users if the protocol is correctly adapted to the individual scenario. -
Activate HTTP/2 on web servers
HTTP/2 offers reduced website load times and other performance benefits, along with the promise of server push. - Next-Generation HTTP/3 Protocol Arrives as a Standard
-
Enlarging the TCP initial window
Linux on-board resources let admins open the floodgates for high-volume TCP packages.
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Most Popular
Support Our Work
ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.
