{"id":84853,"date":"2020-06-11T13:42:33","date_gmt":"2020-06-11T11:42:33","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/predvaritelnyj-vypusk-nginx-s-podderzhkoj-quic-i-http-3"},"modified":"2020-06-11T13:42:33","modified_gmt":"2020-06-11T11:42:33","slug":"predvaritelnyj-vypusk-nginx-s-podderzhkoj-quic-i-http-3","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/predvaritelnyj-vypusk-nginx-s-podderzhkoj-quic-i-http-3","title":{"rendered":"Pre-release of nginx with support for QUIC and HTTP\/3","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

NGINX Company announced<\/a><\/noindex> announces the start of testing implementations<\/a><\/noindex> of QUIC and HTTP\/3 protocols in the HTTP server and proxy nginx. The implementation is based on Draft 27<\/a><\/noindex> of the IETF-QUIC specification and is available through a separate repository<\/a><\/noindex>, branched from release 1.19.0. The code is distributed under a BSD license and does not overlap with the previously proposed<\/a><\/noindex> HTTP\/3 implementation for nginx from Cloudflare, which is a separate project.<\/p>\n

Support for HTTP\/3 in nginx is marked as experimental, as not all features<\/a><\/noindex> of the protocol are implemented. However, nginx can already be used to respond to simple HTTP\/3 requests over QUIC and to upload\/download large files. Some of the currently missing protocol capabilities include version negotiation, ECN and congestion control, structured logs, recovery mode (QUIC recovery, flow and congestion control), NAT Rebinding, mobile addresses, Server push, and data attachment (trailer). Basic support for processing ACK packets and flow control is also proposed, which requires further development. Not all standard requirements are met.<\/p>\n

To activate HTTP\/3, nginx needs to be built with the http_v3_module and an additional 'listen' directive with the 'http3' flag must be added to create a listening UDP socket. For example:
\n\u00ablisten\u00bb with the flag \u00abhttp3\u00bb to create a listening UDP socket. For example:<\/p>\n

server {
\n listen 443 http3 reuseport; # UDP socket for QUIC+HTTP\/3
\n ssl_protocols TLSv1.3; # TLS 1.3 is mandatory in QUIC<\/p>\n

ssl_certificate ssl\/www.example.com.crt;
\n ssl_certificate_key ssl\/www.example.com.key;
\n add_header Alt-Svc 'quic=\":443\"'; # indication of QUIC availability<\/p>\n

add_header Alt-Svc 'quic=\u00bb:443'; # indicates QUIC availability
\n (Quick UDP Internet Connections) has been developed by Google since 2013 as an alternative to the TCP+TLS stack for the Web, solving issues with long connection setup and negotiation times in TCP, and eliminating delays due to packet loss during data transmission. QUIC serves as an overlay on the UDP protocol, supporting multiplexing of multiple connections and providing encryption methods equivalent to TLS\/SSL. On the client-side, experimental support for HTTP\/3 has already been added to
\n }<\/p>\n

It should be noted that HTTP\/3 standardizes the use of the QUIC protocol as a transport for HTTP\/2. The protocol QUIC<\/a><\/noindex> NGINX Company has announced the start of testing Curl<\/a><\/noindex>, Firefox<\/a><\/noindex> and Chromium<\/a><\/noindex>.
\n

\"Pre-release<\/a><\/noindex><\/center><\/p>\n

Key Features<\/a><\/noindex> QUIC:\n<\/p>\n