{"id":99904,"date":"2021-04-17T10:22:46","date_gmt":"2021-04-17T08:22:46","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vklyuchenie-podderzhki-http-3-v-firefox-namecheno-na-konecz-maya"},"modified":"2021-04-17T10:22:46","modified_gmt":"2021-04-17T08:22:46","slug":"vklyuchenie-podderzhki-http-3-v-firefox-namecheno-na-konecz-maya","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vklyuchenie-podderzhki-http-3-v-firefox-namecheno-na-konecz-maya","title":{"rendered":"The support for HTTP\/3 in Firefox is expected to be enabled by the end of May.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Mozilla has announced its intention to begin the phased inclusion of the HTTP\/3 and QUIC protocols in the Firefox 88 release, scheduled for April 19 (initially, the release was expected on April 20, but according to the schedule, it has been moved back by one day). Initially, HTTP\/3 support will be activated only for a small percentage of users and, if no unforeseen issues arise, will be rolled out to everyone by the end of May. In nightly builds and beta versions, HTTP\/3 was enabled by default at the end of March. <\/p>\n

It is worth noting that the implementation of HTTP\/3 in Firefox is based on the neqo project developed by Mozilla, which provides the implementation for the client and server<\/a> for the QUIC protocol. The code components for supporting HTTP\/3 and QUIC are written in Rust. To control the enabling of HTTP\/3 in about:config, the option \"network.http.http3.enabled\" is available. Experimental support for HTTP\/3 has also been added to the client software Chrome and curl, while for servers<\/a> is available in nginx, as well as in the form of the nginx module and a test server from Cloudflare. On the website side, HTTP\/3 support is already provided on servers from Google and Facebook. <\/p>\n

The HTTP\/3 protocol is still in draft specification stage and is not yet standardized by the IETF. To use HTTP\/3, both the client and server must support the same version of the draft QUIC and HTTP\/3 standard, which is indicated in the Alt-Svc header (Firefox supports drafts from 27 to 32). <\/p>\n

HTTP\/3 specifies the use of the QUIC protocol as a transport for HTTP\/2. The QUIC protocol (Quick UDP Internet Connections) has been developed by Google since 2013 as an alternative to the TCP+TLS combination for the Web, addressing issues with long connection setup and negotiation times in TCP and eliminating delays caused by packet loss during data transmission. QUIC is built on top of the UDP protocol, supporting multiplexing of multiple connections and providing encryption methods equivalent to TLS\/SSL. During the development of the standard in the IETF, changes were made to the protocol, leading to the emergence of two parallel branches, one for HTTP\/3, and the other supported by Google (Chrome supports both versions). <\/p>\n

Key features of QUIC: <\/p>\n