HTTP/3 - HTTP over QUIC

Tarayıcı Desteği

Tarayıcımızın HTTP/3 destekleyip desteklemediğini görmek için  quic.nginx.org adresine gidilebilir.

TCP Kullanmıyor, QUIC Kullanıyor

Açıklaması şöyle.

Instead of TCP, HTTP/3 uses a new protocol, developed in 2012 by Google, called QUIC (pronounced “quick”).

QUIC'in Özellikleri

Bazı özellikleri şöyle

- Instead of TCP, HTTP/3 uses a new protocol, QUIC, developed by Google in 2012. QUIC runs over UDP, the User Datagram Protocol.

- QUIC provides native multiplexing, and lost packets only impact the streams where data has been lost. This resolves the head-of-line blocking issue in HTTP/2.

- QUIC provides flow control for stream data and all HTTP/3 frame types that are sent on streams. Therefore, all frame headers and payloads are subject to flow control.

- The request and response headers are compressed by QPACK instead of HPACK in HTTP/2.

- Several HTTP/3 frames are used to manage server push.

Native Multiplexing

Bu sayede sayfayı paralel yüklemek mümkün. Açıklaması şöyle.

Before HTTP/2, browsers could only send one request to the server at a time. This made website loading significantly slower because the browser only loaded one asset, like CSS or JavaScript, at a time. HTTP/2 introduced the ability to load more than one asset at a time, but TCP was not made for this. If one of the requests failed, TCP would make the browser redo all the requests. Because TCP was removed in HTTP/3 and replaced by QUIC, HTTP/3 solved this problem. With HTTP/3, the browser only needs to redo the failed request. Because of this, HTTP/3 is faster and more reliable.

TLS

Açıklaması şöyle. QUIC protokolü de TLS kullanıyor

HTTP/3 optimizes the “handshake” that allows browsers HTTP requests to be encrypted. QUIC combines the initial connection with a TLS handshake, making it secure by default and faster.