{"id":25269,"date":"2019-04-06T04:57:55","date_gmt":"2019-04-06T03:57:55","guid":{"rendered":"https:\/\/staging.kinsta.site\/?p=42574"},"modified":"2022-04-06T14:19:48","modified_gmt":"2022-04-06T13:19:48","slug":"http3","status":"publish","type":"post","link":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/","title":{"rendered":"Qu\u2019est-ce que HTTP\/3 &#8211; Informations sur le nouveau protocole UDP rapide ?"},"content":{"rendered":"<h3><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">TL;DR<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">In November 2018, the Internet Engineering Task Force (IETF) met in Bangkok and a new <\/span><\/span><a href=\"https:\/\/tools.ietf.org\/html\/draft-ietf-quic-http-17\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Internet project<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> was adopted. <\/span><span style=\"vertical-align: inherit\">The QUIC transport protocol, <\/span><\/span><a href=\"https:\/\/staging.kinsta.site\/fr\/apprendre\/http2\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">the successor to HTTP\/2<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , has been renamed to HTTP\/3.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">HTTP\/3 relies on UDP and is already used by major Internet companies such as Google and Facebook. <\/span><span style=\"vertical-align: inherit\">If you&rsquo;re using Chrome and connecting to a Google service, you&rsquo;re probably already using QUIC.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">The new version of the HTTP protocol takes advantage of the bare-metal, low-level UDP protocol, and defines many of the new features that were in previous versions of the HTTP protocol on the TCP layer. <\/span><span style=\"vertical-align: inherit\">This solves the constraints within the existing Internet infrastructure.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Early results are promising, and when the IETF Internet Draft expires in August 2021, we can expect HTTP\/3 to be introduced as a new third-generation HTTP standard.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"><div><\/div><kinsta-auto-toc heading=\"Table of Contents\" exclude=\"last\" list-style=\"arrow\" selector=\"h2\" count-number=\"-1\"><\/kinsta-auto-toc><\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">[shareable-quote tweet=\u00a0\u00bbJust like with HTTP\/2, HTTP\/3 will again build on these achievements to help speed up the web. ?\u00a0\u00bb user=\u00a0\u00bbKinsta_FR\u00a0\u00bb hashtags=\u00a0\u00bbHTTP3,webperf\u00a0\u00bb]<\/span><\/span><\/p>\n<h2 id=\"http3-coming\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Progress of HTTP\/3 in 2026<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Some say the web industry&rsquo;s thirst for speed and latency is matched only by Google Chrome&rsquo;s thirst for more RAM.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">A few years ago, <\/span><\/span><a href=\"https:\/\/staging.kinsta.site\/fr\/apprendre\/http2\/\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">we published an article on HTTP\/2<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , a standard which, <\/span><\/span><a href=\"https:\/\/w3techs.com\/technologies\/details\/ce-http2\/all\/all\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">according to W3Techs<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , has now achieved a global adoption rate of around 45%. <\/span><span style=\"vertical-align: inherit\">And according to <\/span><\/span><a href=\"https:\/\/caniuse.com\/#search=http2\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Can I Use<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , it&rsquo;s also supported by all modern web browsers. <\/span><span style=\"vertical-align: inherit\">However, here we are writing an article about the next version of the protocol, HTTP\/3.<\/span><\/span><\/p>\n<figure id=\"attachment_97389\" aria-describedby=\"caption-attachment-97389\" style=\"width: 1760px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-97389 size-full\" src=\"https:\/\/staging.kinsta.site\/wp-content\/uploads\/2019\/03\/http2-adoption-chart.png\" alt=\"HTTP\/2 adoption trend.\" width=\"1760\" height=\"1260\"><figcaption id=\"caption-attachment-97389\" class=\"wp-caption-text\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">HTTP\/2 adoption trend.<\/span><\/span><\/figcaption><\/figure>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">HTTP\/3 is, at the time of this writing, an <\/span><\/span><a href=\"https:\/\/tools.ietf.org\/html\/draft-ietf-quic-http-18\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Internet-Draft or <\/span><\/span><\/a><a href=\"https:\/\/tools.ietf.org\/html\/draft-ietf-quic-http-18\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">IETF<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> ID <\/span><span style=\"vertical-align: inherit\">, which means it is currently under consideration for a future Internet standard by the <\/span><\/span><a href=\"https:\/\/www.ietf.org\/about\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Internet Engineering Task Force<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> &#8211; an <\/span><span style=\"vertical-align: inherit\">international <\/span><i><span style=\"vertical-align: inherit\">Internet standards <\/span><\/i><\/span><i><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">body<\/span><\/span><\/i><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , responsible for defining and promoting approved Internet protocol standards, such as TCP, <\/span><a href=\"https:\/\/staging.kinsta.site\/fr\/blog\/ipv4-vs-ipv6\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\">IPv6<\/span><\/a><span style=\"vertical-align: inherit\"> , VoIP, Internet of Things, etc.<\/span><\/span><i><\/i><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">It is an open body that brings together the web industry and facilitates discussions on the direction of the Internet. <\/span><span style=\"vertical-align: inherit\">Currently, the \u00ab\u00a0Internet Draft\u00a0\u00bb phase of HTTP\/3 is the last phase before proposals are promoted to the Request-for-Comments ( <\/span><\/span><a href=\"https:\/\/www.ietf.org\/blog\/how-read-rfc\/\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">RFC<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> ) level, which we can consider, for all intents and purposes, as official definitions of the Internet protocol.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Although HTTP\/3 is not yet an official Internet protocol, many companies and projects have already started adding support for HTTP\/3 in their products.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">\n<div  class=\"featured-snippet\" id=\"what-is-http3\">\n    <div class=\"featured-snippet__content\">\n        <h2>Qu&#039;est-ce que le HTTP\/3 - En termes simples ?<\/h2>\n        <div><p>HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. QUIC (Quick UDP Internet Connections) a \u00e9t\u00e9 initialement d\u00e9velopp\u00e9 par Google et est le successeur de HTTP\/2. Des entreprises comme Google et Facebook utilisent d\u00e9j\u00e0 QUIC pour acc\u00e9l\u00e9rer le Web.<\/p>\n<\/div>\n    <\/div>\n    <div class=\"featured-snippet__footer\">\n        <div class=\"arrow-down\"><\/div>\n        <div class=\"featured-snippet__footer--content row nocol middle-xs between-xs reverse\">\n            <div style=\"margin-left: auto; position: relative; top: -1px\" class=\"row nocol middle-xs\">\n                <div class=\"color--mediumGray\" style=\"font-size: 14px; vertical-align: middle;\">\n                    <svg  class=\"icon icon--logo display--block\" aria-hidden=\"true\" focusable=\"false\"><use xlink:href=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/themes\/kinsta\/dist\/sprite.svg?v=e8af2143e3b8bceb5561b327e81ec085#logo\" \/><\/svg>                <\/div>\n                <div class=\"text--bold color--mediumGray\" style=\"padding-left: 3px;\">Support<\/div>\n            <\/div>\n        <\/div>\n    <\/div>\n<\/div>\n<\/span><\/span><\/p>\n<h3><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">HTTP\/3 support by web browsers<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">As <\/span><\/span><a href=\"https:\/\/caniuse.com\/http3\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">for web browsers<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , Chrome v87, Firefox v88, and Edge v87 all have HTTP\/3 enabled by default. <\/span><span style=\"vertical-align: inherit\">For Safari users, the option to enable HTTP\/3 was added in Safari Technology Preview v104. <\/span><span style=\"vertical-align: inherit\">However, HTTP\/3 support is not yet available in the stable version of Safari.<\/span><\/span><\/p>\n<h3><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Library support for HTTP\/3<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">For developers looking to leverage HTTP\/3 technologies, many popular libraries have already added support for HTTP\/3. <\/span><span style=\"vertical-align: inherit\">Since HTTP\/3 is still in the Internet Draft stage, you should make sure you are aware of the latest updates when working with any of the libraries below.<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Python \u2013 <\/span><\/span><a href=\"https:\/\/pypi.org\/project\/http3\/\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">http3<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> and <\/span><\/span><a href=\"https:\/\/pypi.org\/project\/aioquic\/\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">aioquic<\/span><\/span><\/a><\/li>\n<li><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Rust \u2013 <\/span><\/span><a href=\"https:\/\/github.com\/cloudflare\/quiche\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">quiche<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , <\/span><\/span><a href=\"https:\/\/github.com\/mozilla\/neqo\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">neqo<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> , and <\/span><\/span><a href=\"https:\/\/github.com\/quinn-rs\/quinn\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">quinn<\/span><\/span><\/a><\/li>\n<li><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">C \u2013 <\/span><\/span><a href=\"https:\/\/github.com\/ngtcp2\/nghttp3\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">nghttp3<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> and <\/span><\/span><a href=\"https:\/\/github.com\/litespeedtech\/lsquic\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">lsquic<\/span><\/span><\/a><\/li>\n<li><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Go \u2013 <\/span><\/span><a href=\"https:\/\/github.com\/lucas-clemente\/quic-go\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">quicgo<\/span><\/span><\/a><\/li>\n<li><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">JavaScript- <\/span><\/span><a href=\"https:\/\/staging.kinsta.site\/fr\/base-de-connaissances\/qu-est-ce-que-node-js\/\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Node.js<\/span><\/span><\/a><\/li>\n<\/ul>\n<h3><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Framework support for HTTP\/3<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">On the infrastructure side, Cloudflare led the way by supporting HTTP\/3 across its entire edge network. <\/span><span style=\"vertical-align: inherit\">This means sites with Cloudflare enabled can take advantage of the security and performance improvements of HTTP\/3 without any additional work.<\/span><\/span><\/p>\n<p>Chez Kinsta, tous les sites que nous h\u00e9bergeons sont prot\u00e9g\u00e9s par notre <a href=\"https:\/\/staging.kinsta.site\/fr\/integration-cloudflare\/\">int\u00e9gration gratuite de Cloudflare<\/a>. En plus d&rsquo;un pare-feu de niveau entreprise et d&rsquo;une protection DDoS, les clients de Kinsta ont \u00e9galement acc\u00e8s \u00e0 HTTP\/3 !<\/p>\n<p>Pour tester si votre site prend en charge HTTP\/3, vous pouvez utiliser l&rsquo;<a href=\"https:\/\/gf.dev\/http3-test\">outil de test HTTP\/3 de Geekflare<\/a>. Il suffit de saisir votre domaine et de cliquer sur le bouton \u00ab Check HTTP\/3 \u00bb, et l&rsquo;outil vous fera savoir si votre site est compatible avec HTTP\/3.<\/p>\n<figure id=\"attachment_97390\" aria-describedby=\"caption-attachment-97390\" style=\"width: 1500px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-97390 size-full\" src=\"https:\/\/staging.kinsta.site\/wp-content\/uploads\/2019\/03\/geekflare-http3-testing-tool.jpg\" alt=\"Geekflare's HTTP\/3 testing tool.\" width=\"1500\" height=\"799\"><figcaption id=\"caption-attachment-97390\" class=\"wp-caption-text\">Outil de test HTTP\/3 de Geekflare.<\/figcaption><\/figure>\n<p>Si votre site prend en charge HTTP\/3, vous devriez voir un message comme celui ci-dessous. Comme kinstalife.com est h\u00e9berg\u00e9 sur Kinsta, HTTP\/3 est enti\u00e8rement pris en charge gr\u00e2ce \u00e0 notre int\u00e9gration Cloudflare.<\/p>\n<figure id=\"attachment_97391\" aria-describedby=\"caption-attachment-97391\" style=\"width: 1500px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-97391 size-full\" src=\"https:\/\/staging.kinsta.site\/wp-content\/uploads\/2019\/03\/http3-on-kinsta.jpg\" alt=\"Kinsta supports HTTP\/3 connections.\" width=\"1500\" height=\"800\"><figcaption id=\"caption-attachment-97391\" class=\"wp-caption-text\">Kinsta prend en charge les connexions HTTP\/3.<\/figcaption><\/figure>\n<p>Vous pouvez \u00e9galement utiliser l&rsquo;inspecteur de votre navigateur pour v\u00e9rifier la prise en charge de HTTP\/3. Pour cet exemple, nous utiliserons la derni\u00e8re version de Google Chrome qui prend en charge HTTP\/3.<\/p>\n<p>Pour ouvrir l&rsquo;inspecteur, faites un clic droit sur la page et cliquez sur \u00ab Inspecter \u00bb, puis acc\u00e9dez \u00e0 l&rsquo;onglet \u00ab R\u00e9seau \u00bb. Dans la colonne \u00ab Protocole \u00bb, vous pouvez voir le protocole HTTP utilis\u00e9 pour la connexion. Les connexions HTTP\/2 apparaissent sous la forme \u00ab h2 \u00bb, tandis que les connexions HTTP\/3 apparaissent sous la forme \u00ab h3-XX \u00bb (XX fait r\u00e9f\u00e9rence \u00e0 un projet HTTP\/3 sp\u00e9cifique). Comme vous pouvez le voir dans l&rsquo;image ci-dessous, kinstalife.com prend en charge les connexions sur \u00ab h3-29 \u00bb, ce qui signifie \u00ab HTTP\/3 Draft 29 \u00bb.<\/p>\n<figure id=\"attachment_97392\" aria-describedby=\"caption-attachment-97392\" style=\"width: 1500px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-97392 size-full\" src=\"https:\/\/staging.kinsta.site\/wp-content\/uploads\/2019\/03\/check-http3-support-browser.jpg\" alt=\"Chrome supports the h3-29 protocol.\" width=\"1500\" height=\"733\"><figcaption id=\"caption-attachment-97392\" class=\"wp-caption-text\">Chrome prend en charge le protocole h3-29.<\/figcaption><\/figure>\n<p>Maintenant que nous avons pass\u00e9 en revue l&rsquo;\u00e9tat actuel de HTTP\/3, plongeons dans les diff\u00e9rences entre HTTP\/2 et HTTP\/3 !<\/p>\n<h2 id=\"background-http2\">Retour en arri\u00e8re &#8211; \u00c7a a commenc\u00e9 avec HTTP\/2<\/h2>\n<p>HTTP\/2 a apport\u00e9 de s\u00e9rieuses am\u00e9liorations avec des <a href=\"https:\/\/www.sitepoint.com\/http2-background-performance-benefits-implementations\/\" target=\"_blank\" rel=\"noopener noreferrer\">t\u00e9l\u00e9chargements non bloquants, des pipelines et les<\/a> serveurs push qui nous ont aid\u00e9 \u00e0 surmonter certaines limitations du protocole TCP sous-jacent. Cela nous a permis de r\u00e9duire au minimum le nombre de cycles de requ\u00eates-r\u00e9ponses.<\/p>\n<p>HTTP\/2 permettait de pousser plus d&rsquo;une ressource dans une seule connexion TCP &#8211; le multiplexage. Nous avons \u00e9galement obtenu plus de flexibilit\u00e9 dans l&rsquo;ordre des t\u00e9l\u00e9chargements statiques, et nos pages ne sont maintenant plus limit\u00e9es par une progression lin\u00e9aire des t\u00e9l\u00e9chargements.<\/p>\n<figure style=\"width: 500px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2016\/04\/push-http2.png\" alt=\"HTTP\/2 push\" width=\"500\" height=\"244\"><figcaption class=\"wp-caption-text\">Push HTTP\/2<\/figcaption><\/figure>\n<p>En pratique, cela signifie qu&rsquo;une ressource javascript importante n&rsquo;\u00e9quivaut pas n\u00e9cessairement \u00e0 un point d&rsquo;\u00e9tranglement pour toutes les autres ressources statiques qui attendent leur tour.<\/p>\n<figure style=\"width: 2880px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/pas-pipelining-pipelining.png\" alt=\"No pipelining vs pipelining\" width=\"2880\" height=\"2003\"><figcaption class=\"wp-caption-text\">Pas de pipelining vs pipelining (Source de l&rsquo;image : <a href=\"https:\/\/commons.wikimedia.org\/wiki\/File:HTTP_pipelining2.svg#\/media\/File:HTTP_pipelining2.svg\" target=\"_blank\" rel=\"noopener noreferrer\">Wikipedia<\/a>, Author Mwhitlock)<\/figcaption><\/figure>\n<p>Ajoutez \u00e0 cela la compression HPACK de l&rsquo;en-t\u00eate HTTP\/2 et le format binaire par d\u00e9faut du transfert de donn\u00e9es, et nous avons, dans de nombreux cas, un protocole beaucoup plus efficace.<\/p>\n<figure style=\"width: 942px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2016\/04\/compression-http2-hpack.png\" alt=\"HTTP\/2 HPACK Compression\" width=\"942\" height=\"375\"><figcaption class=\"wp-caption-text\">Compression HTTP\/2 HPACK<\/figcaption><\/figure>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Major browser implementations made it necessary to implement encryption &#8211; SSL &#8211; in order to take advantage of the benefits of HTTP\/2 &#8211; and sometimes this resulted in a computational overhead that made the speed improvements unnoticeable. <\/span><span style=\"vertical-align: inherit\">There have even been instances where users have reported a slowdown after transitioning to HTTP\/2.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Let&rsquo;s just say that the early days of adopting this build weren&rsquo;t for the faint of heart.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">The Nginx implementation also lacked the server push feature, relying on a module. <\/span><span style=\"vertical-align: inherit\">And <\/span><\/span><a href=\"https:\/\/staging.kinsta.site\/fr\/blog\/nginx-vs-apache\/\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Nginx modules aren&rsquo;t the<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> usual Apache modules you can just copy &#8211; NGINX needs to be recompiled with those.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Although some of these issues are now resolved, if we look at the entire protocol stack, we see that the main constraint is at a lower level than HTTP\/2 dared to attempt.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">To elaborate on this, we will dissect today&rsquo;s Internet Protocol stack from its bottom layer upwards. <\/span><span style=\"vertical-align: inherit\">If you want to know more about the background of HTTP\/2, feel free to check out our <\/span><\/span><a href=\"https:\/\/staging.kinsta.site\/fr\/apprendre\/http2\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">ultimate HTTP\/2 guide<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> .<\/span><\/span><\/p>\n<h2 id=\"internet-protocol\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Internet Protocol (IP)<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">The Internet Protocol (IP) defines the bottom part of the entire Internet topology. <\/span><span style=\"vertical-align: inherit\">It&rsquo;s the part of the internet stack that is, we can say, really non-negotiable without changing everything, including replacing all of the hardware infrastructure, from routers to servers and even end-user machines.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">So, while protocol review may be due, such a massive undertaking isn&rsquo;t on the horizon at this time, primarily because we haven&rsquo;t yet found a viable, game-changing alternative. , but consistent with the past.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">The beginnings of the IP protocol date back to 1974, with a paper published by the <\/span><\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/Institute_of_Electrical_and_Electronic_Engineers\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Institute of Electrical and Electronics Engineers<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> and authored by Vint Cerf and Bob Cahn. <\/span><span style=\"vertical-align: inherit\">It details packets sent over a network, routes them through IP addresses and defined numeric addresses of nodes in a network\/networks. <\/span><span style=\"vertical-align: inherit\">The protocol defined the format of these packets, or datagrams &#8211; its headers and its payload.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">After the definition in <\/span><\/span><a href=\"https:\/\/tools.ietf.org\/html\/rfc760\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">RFC 760<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> of 1980, the IETF adopted the definition widely used to this day, in its <\/span><\/span><a href=\"https:\/\/tools.ietf.org\/html\/rfc791\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Request for Comments 791<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> . <\/span><span style=\"vertical-align: inherit\">This is the fourth version of the protocol, but we can say that it is the first version in production.<\/span><\/span><\/p>\n<figure style=\"width: 1206px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/protocole-internet-rfc791.png\" alt=\"Internet Protocol (RFC791)\" width=\"1206\" height=\"1848\"><figcaption class=\"wp-caption-text\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Internet Protocol (Image source: <\/span><\/span><a href=\"https:\/\/tools.ietf.org\/html\/rfc791\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">RFC791<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> )<\/span><\/span><\/figcaption><\/figure>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">It uses 32-bit addresses, which limits the number of addresses to around 4 billion. <\/span><span style=\"vertical-align: inherit\">This limitation explains the mystery of why non-professional Internet users obtain \u00ab\u00a0dynamic IP addresses\u00a0\u00bb from their ISP, and a static IP is considered \u00ab\u00a0added value\u00a0\u00bb and often subject to additional charges.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">They are rationing.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">It didn&rsquo;t take long before it was realized that 32-bit addresses were not enough and the shortage was imminent, so many RFCs were published in an attempt to remedy this. <\/span><span style=\"vertical-align: inherit\">Although these solutions are <\/span><\/span><a href=\"https:\/\/en.m.wikipedia.org\/wiki\/Classless_Inter-Domain_Routing\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">widely used today<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> and are part of our daily lives, it is probably safe to say that they are very popular.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Internet <\/span><\/span><a href=\"https:\/\/staging.kinsta.site\/fr\/blog\/ipv4-vs-ipv6\/#what-is-ipv6\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Protocol version 6 or IPv6<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> came as a way to address these limitations, including being gradually adopted over the previous version. <\/span><span style=\"vertical-align: inherit\">It became a draft standard for the IETF in 1998 and was elevated to an Internet standard in 2017.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">While the IPv4 address space was limited by its 32-bit address length, the IPv6 standard was 128 bits, or 3.4*10^38 possible addresses. <\/span><span style=\"vertical-align: inherit\">That should be enough to last us a while.<\/span><\/span><\/p>\n<p class=\"p1\"><kinsta-video src=\"https:\/\/www.youtube.com\/watch?v=U-22FneZhd0\"><\/kinsta-video><\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">According to <\/span><\/span><a href=\"https:\/\/www.google.com\/intl\/en\/ipv6\/statistics.html#tab=ipv6-adoption\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Google<\/span><\/span><\/a><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\"> and IPv6 connectivity among its users, IPv6 adoption is just over 35% as of June 2021.<\/span><\/span><\/p>\n<figure style=\"width: 1928px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/adoption-d-ipv6.png\" alt=\"Adoption of IPv6\" width=\"1928\" height=\"1166\"><figcaption class=\"wp-caption-text\"><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Adoption of IPv6<\/span><\/span><\/figcaption><\/figure>\n<p>L&rsquo;IP est une couche rudimentaire de la pile Internet, d\u00e9finissant la plupart des choses de base, sans garantie de livraison, d&rsquo;int\u00e9grit\u00e9 des donn\u00e9es, ou de commande des paquets transmis. \u00c0 lui seul, il n&rsquo;est pas fiable. Le format d&rsquo;en-t\u00eate d&rsquo;IPv4 fournit la somme de contr\u00f4le d&rsquo;en-t\u00eate que les n\u0153uds de transmission utilisent pour v\u00e9rifier l&rsquo;int\u00e9grit\u00e9 de l&rsquo;en-t\u00eate. Cela le rend diff\u00e9rent de la version IPv6, qui s&rsquo;appuie sur la couche de liaison en dessous, ce qui lui permet d&rsquo;\u00eatre plus rapide.<\/p>\n<figure style=\"width: 1424px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/internet-datagram-header.png\" alt=\"Internet Datagram Header\" width=\"1424\" height=\"742\"><figcaption class=\"wp-caption-text\">Internet Datagram Header (Source de l&rsquo;image : <a href=\"https:\/\/tools.ietf.org\/html\/rfc791\" target=\"_blank\" rel=\"noopener noreferrer\">RFC791<\/a>)<\/figcaption><\/figure>\n<h2 id=\"tcp-udp\">Comprendre le r\u00f4le du TCP et UDP<\/h2>\n<p>Maintenant, il est temps d&rsquo;explorer o\u00f9 HTTP\/3 s&rsquo;int\u00e8gre avec TCP et UDP.<\/p>\n<h3>TCP<\/h3>\n<p>Alors que l&rsquo;IP est la couche sous-jacente de toutes nos communications en ligne aujourd&rsquo;hui, le <a href=\"https:\/\/en.m.wikipedia.org\/wiki\/Transmission_Control_Protocol\" target=\"_blank\" rel=\"noopener noreferrer\">TCP (Transmission Control Protocol)<\/a> est une partie de plus haut niveau de la suite de protocoles Internet, fournissant la fiabilit\u00e9 n\u00e9cessaire pour le Web, le courrier, le transfert de fichiers (FTP) &#8211; pour les couches d&rsquo;applications\/protocoles de l&rsquo;Internet.<\/p>\n<p>Cela comprend l&rsquo;\u00e9tablissement d&rsquo;une connexion \u00e0 plusieurs \u00e9tapes, l&rsquo;ordre assur\u00e9 des paquets et la retransmission des paquets perdus. Il fournit un feedback (Acks) de la livraison \u00e0 l&rsquo;exp\u00e9diteur et ainsi de suite. Il y a aussi le calcul de la somme de contr\u00f4le pour d\u00e9tecter les erreurs.<\/p>\n<p>Toutes ces choses indiquent un grand nombre d&rsquo;\u00e9tapes qui font de TCP un protocole fiable, ce qui en fait le fondement des services Internet les plus c\u00e9l\u00e8bres que nous utilisons aujourd&rsquo;hui.<\/p>\n<p>Ses sp\u00e9cifications <a href=\"https:\/\/tools.ietf.org\/html\/rfc675\" target=\"_blank\" rel=\"noopener noreferrer\">remontant \u00e0 1974 (RFC 675)<\/a> et <a href=\"https:\/\/tools.ietf.org\/html\/rfc793\" target=\"_blank\" rel=\"noopener noreferrer\">1981 (RFC 793)<\/a> n&rsquo;ont pas beaucoup chang\u00e9 \u00e0 ce jour.<\/p>\n<p>La fiabilit\u00e9 que fournit TCP n&rsquo;est cependant pas sans co\u00fbt. Les frais g\u00e9n\u00e9raux de tous les allers-retours requis par les prises de contact, les retours de livraison, les commandes de garanties et les sommes de contr\u00f4le qui pourraient \u00eatre consid\u00e9r\u00e9s comme faibles et redondants. Il a fait de TCP un goulot d&rsquo;\u00e9tranglement de la pile de protocoles moderne. HTTP\/2 a atteint un plateau d&rsquo;am\u00e9liorations de vitesse qui peuvent \u00eatre r\u00e9alis\u00e9es sur TCP.<\/p>\n<p>Changer le TCP de mani\u00e8re substantielle n&rsquo;est pas une t\u00e2che simple, car le protocole fait partie de la pile TCP\/IP qui remonte aux ann\u00e9es 70. Cela est profond\u00e9ment ancr\u00e9 dans les syst\u00e8mes d&rsquo;exploitation, le micrologiciel de l&rsquo;appareil, etc.<\/p>\n<h3>UDP<\/h3>\n<p>UDP (<a href=\"https:\/\/en.m.wikipedia.org\/wiki\/User_Datagram_Protocol\" target=\"_blank\" rel=\"noopener noreferrer\">User Datagram Protocol<\/a>) est \u00e9galement l&rsquo;une des parties de la suite de protocole Internet, avec ses sp\u00e9cifications qui remontent \u00e0 <a href=\"https:\/\/tools.ietf.org\/html\/rfc768\" target=\"_blank\" rel=\"noopener noreferrer\">1980 (RFC 768)<\/a>.<\/p>\n<p>Il s&rsquo;agit, comme son nom l&rsquo;indique, d&rsquo;un protocole sans connexion bas\u00e9 sur un datagramme. Ce qui signifie qu&rsquo;il n&rsquo;y a pas de prise de contact et qu&rsquo;il n&rsquo;y a aucune garantie de commande ou de livraison. Cela signifie que toutes les \u00e9tapes possibles pour assurer la livraison, l&rsquo;int\u00e9grit\u00e9 des donn\u00e9es et d&rsquo;autres choses sont laiss\u00e9es sur la couche application. Cela signifie qu&rsquo;une application construite sur UDP peut choisir les strat\u00e9gies qu&rsquo;elle utilisera en fonction du cas concret, ou qu&rsquo;elle peut \u00e9ventuellement utiliser des \u00e9l\u00e9ments de la <a href=\"https:\/\/en.m.wikipedia.org\/wiki\/Link_layer\" target=\"_blank\" rel=\"noopener noreferrer\">couche de lien<\/a>, comme les sommes de contr\u00f4le, pour \u00e9viter les frais g\u00e9n\u00e9raux.<\/p>\n<p>\u00c9tant donn\u00e9 que le protocole UDP est tr\u00e8s r\u00e9pandu, tout comme le protocole TCP, il permet d&rsquo;apporter des am\u00e9liorations sans n\u00e9cessiter de mises \u00e0 jour des firmwares d&rsquo;un grand nombre d&rsquo;appareils connect\u00e9s \u00e0 Internet, ni de modifications importantes des syst\u00e8mes d&rsquo;exploitation.<\/p>\n<blockquote><p>Le d\u00e9ploiement de nouveaux protocoles est entrav\u00e9 par de nombreux pare-feu, NATs, routeurs et autres middle-box qui n&rsquo;autorisent que le d\u00e9ploiement TCP ou UDP entre les utilisateurs et les serveurs qu&rsquo;ils doivent atteindre. &#8211; <a href=\"https:\/\/daniel.haxx.se\/http3-explained\/\" target=\"_blank\" rel=\"noopener noreferrer\">Explication de HTTP\/3<\/a><\/p><\/blockquote>\n<p>Ce <a href=\"https:\/\/news.ycombinator.com\/item?id=12021195\" target=\"_blank\" rel=\"noopener noreferrer\">fil de discussion sur Hacker News<\/a> peut nous aider \u00e0 commencer \u00e0 comprendre le raisonnement derri\u00e8re la construction de la nouvelle version HTTP sur la pile r\u00e9seau existante, plut\u00f4t que de la r\u00e9inventer (bien qu&rsquo;il y ait plus que cela).<\/p>\n<p>La sp\u00e9cification du format de paquet UDP est plut\u00f4t minimale, son en-t\u00eate se compose du port source, du port de destination, de la longueur, en octets, de l&rsquo;en-t\u00eate du paquet et des donn\u00e9es du paquet et de la somme de contr\u00f4le. La somme de contr\u00f4le peut \u00eatre utilis\u00e9e pour v\u00e9rifier l&rsquo;int\u00e9grit\u00e9 des donn\u00e9es tant pour l&rsquo;en-t\u00eate que pour la partie donn\u00e9es du paquet.<\/p>\n<p>La somme de contr\u00f4le est facultative lorsque la couche de protocole sous-jacente est IPv4, et obligatoire avec IPv6. Jusqu&rsquo;\u00e0 pr\u00e9sent, l&rsquo;UDP a \u00e9t\u00e9 utilis\u00e9 pour des choses comme la synchronisation de l&rsquo;horloge des syst\u00e8mes informatiques (<a href=\"https:\/\/en.wikipedia.org\/wiki\/Network_Time_Protocol\">NTP<\/a>), applications VoIP, le streaming vid\u00e9o, le syst\u00e8me DNS et le <a href=\"https:\/\/en.m.wikipedia.org\/wiki\/Dynamic_Host_Configuration_Protocol\" target=\"_blank\" rel=\"noopener noreferrer\">protocole DHCP<\/a>.<\/p>\n<h2 id=\"quic-http3\">QUIC et HTTP\/3<\/h2>\n<p>QUIC (Quick UDP Internet Connections) a \u00e9t\u00e9 d\u00e9ploy\u00e9 pour la premi\u00e8re fois par Google en 2012. Il red\u00e9finit les limites des couches r\u00e9seau en s&rsquo;appuyant sur le protocole UDP de niveau inf\u00e9rieur, en red\u00e9finissant les prises de contact, les fonctions de fiabilit\u00e9 et les fonctions de s\u00e9curit\u00e9 dans \u00ab\u00a0l&rsquo;espace utilisateur\u00a0\u00bb, ce qui \u00e9vite d&rsquo;avoir \u00e0 mettre \u00e0 niveau les noyaux des syst\u00e8mes Internet.<\/p>\n<figure style=\"width: 1865px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http2-stack-vs-http3-stack.png\" alt=\"HTTP\/2 stack vs. HTTP\/3 stack\" width=\"1865\" height=\"671\"><figcaption class=\"wp-caption-text\">HTTP\/2 stack vs HTTP\/3 stack<\/figcaption><\/figure>\n<p>Tout comme avec HTTP\/2, une avanc\u00e9e qui a \u00e9t\u00e9 men\u00e9e par Google <a href=\"https:\/\/staging.kinsta.site\/docs\/kinsta-cdn\/\" target=\"_blank\" rel=\"noopener noreferrer\">SPDY<\/a> ou Speedy, HTTP\/3 s&rsquo;appuiera \u00e0 nouveau sur ces r\u00e9alisations.<\/p>\n<p>Bien que HTTP\/2 nous ait donn\u00e9 le multiplexage et att\u00e9nu\u00e9 le blocage en t\u00eate de ligne, il est limit\u00e9 par TCP. Vous pouvez utiliser une seule connexion TCP pour plusieurs flux multiplex\u00e9s ensemble pour transf\u00e9rer des donn\u00e9es, mais lorsque l&rsquo;un de ces flux subit une perte de paquets, <strong>toute la connexion (et tous ses flux) sont retenus en otage, pour ainsi dire<\/strong>, jusqu&rsquo;\u00e0 ce que TCP fasse son travail (retransmettre le paquet perdu).<\/p>\n<p>Cela signifie que tous les paquets, m\u00eame s&rsquo;ils sont d\u00e9j\u00e0 transmis et en attente, sont bloqu\u00e9s dans le tampon du noeud de destination jusqu&rsquo;\u00e0 ce que le paquet perdu soit retransmis. <a href=\"https:\/\/daniel.haxx.se\/\" target=\"_blank\" rel=\"noopener noreferrer\">Daniel Stenberg<\/a> dans son <a href=\"https:\/\/legacy.gitbook.com\/book\/bagder\/http3-explained\/details\" target=\"_blank\" rel=\"noopener noreferrer\">livre sur http\/3<\/a> appelle \u00e7a un \u00ab\u00a0bloc de t\u00eate de ligne bas\u00e9 sur TCP\u00a0\u00bb. Il affirme qu&rsquo;avec 2% de perte de paquets, les utilisateurs feront mieux avec HTTP\/1, avec six connexions pour couvrir ce risque.<\/p>\n<p><strong>QUIC n&rsquo;est pas contraint par cela.<\/strong> Avec QUIC s&rsquo;appuyant sur le protocole UDP connectionless, le concept de connexion n&rsquo;a pas les limites de TCP et les \u00e9checs d&rsquo;un flux n&rsquo;ont pas \u00e0 influencer le reste.<\/p>\n<p>Comme l&rsquo;a dit <a href=\"https:\/\/twitter.com\/SimmerVigor\" target=\"_blank\" rel=\"noopener noreferrer\">Lucas Pardue<\/a> de Cloudflare :<\/p>\n<figure style=\"width: 1091px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/Lucas-pardue-http3.png\" alt=\"Lucas Pardue on HTTP\/3\" width=\"1091\" height=\"381\"><figcaption class=\"wp-caption-text\">Lucas Pardue sur HTTP\/3<\/figcaption><\/figure>\n<p>En mettant l&rsquo;accent sur les <i>flux<\/i> UDP, QUIC r\u00e9alise le multiplexage sans avoir \u00e0 utiliser une seule connexion TCP. QUIC construit sa <i>connexion \u00e0<\/i> un niveau plus \u00e9lev\u00e9 que TCP. Les nouveaux flux dans les connexions QUIC ne sont pas oblig\u00e9s d&rsquo;attendre que les autres se terminent. Les connexions QUIC b\u00e9n\u00e9ficient \u00e9galement de l&rsquo;\u00e9limination de la surcharge du handshake TCP, ce qui r\u00e9duit la latence.<\/p>\n<p>Les gens de Cisco ont fait une vid\u00e9o int\u00e9ressante expliquant la prise de contact \u00e0 3 voies de TCP:<\/p>\n<p>https:\/\/www.youtube.com\/watch?v=LyDqA-dAPW4<\/p>\n<p>Alors que QUIC supprime les fonctions de fiabilit\u00e9 TCP, il compense par la couche UDP, en assurant la retransmission des paquets, la commande, etc. Google Cloud Platform <a href=\"https:\/\/cloudplatform.googleblog.com\/2018\/06\/Introducing-QUIC-support-for-HTTPS-load-balancing.html\" target=\"_blank\" rel=\"noopener noreferrer\">a introduit le support QUIC<\/a> pour ses load balancers en 2018 et a vu une <strong>am\u00e9lioration du temps moyen de chargement des pages de 8% au niveau mondial<\/strong>, et jusqu&rsquo;\u00e0 13% dans les r\u00e9gions o\u00f9 la latence est plus \u00e9lev\u00e9e.<\/p>\n<p>Entre Google Chrome, YouTube, Gmail, la recherche de Google et d&rsquo;autres services, Google a pu d\u00e9ployer QUIC sur une bonne partie d&rsquo;Internet, sans attendre l&rsquo;IETF. Les ing\u00e9nieurs de Google affirment qu&rsquo;en 2017, 7% du trafic Internet \u00e9tait d\u00e9j\u00e0 r\u00e9alis\u00e9 sur QUIC.<\/p>\n<p>La version de QUIC de Google se concentrait uniquement sur le transport HTTP, en utilisant la syntaxe HTTP\/2. Les gens de l&rsquo;IETF (ceux en charge de la standardisation de QUIC), ont d\u00e9cid\u00e9 que la version IETF de QUIC devrait \u00eatre capable de transporter plus que seulement HTTP. Pour l&rsquo;instant, cependant, tout travail sur les protocoles autres que le protocole HTTP sur QUIC est en suspens.<\/p>\n<p>Le groupe de travail de l&rsquo;IETF a \u00e9galement d\u00e9cid\u00e9 que la version standardis\u00e9e utilisera le cryptage<a href=\"https:\/\/staging.kinsta.site\/fr\/blog\/tls-1-3\/\" target=\"_blank\" rel=\"noopener noreferrer\"> TLS 1.3<\/a> au lieu de la solution personnalis\u00e9e de Google. TLS 1.3, par rapport aux anciennes versions, contribue \u00e9galement \u00e0 la vitesse du protocole, car ses prises de contact n\u00e9cessitent moins d&rsquo;aller-retour. <strong>Kinsta supporte le TLS 1.3 sur tous nos serveurs et notre CDN Kinsta.<br \/>\n<\/strong><\/p>\n<p>Actuellement, Google continue d&rsquo;utiliser sa propre version de QUIC dans son produit, tout en orientant ses efforts de d\u00e9veloppement vers les normes IETF. La plupart des autres acteurs de l&rsquo;Internet s&rsquo;appuient sur la version de l&rsquo;IETF (les deux diff\u00e8rent sur d&rsquo;autres aspects que le cryptage).<\/p>\n<p>Si nous ouvrons Chrome Dev Tools et chargeons certains produits Google, comme Gmail, dans la colonne Protocole de l&rsquo;onglet R\u00e9seau, nous verrons beaucoup de ressources charg\u00e9es via la version Google du protocole QUIC. C&rsquo;est \u00e9galement le cas pour les produits Google comme Analytics, Google Tag Manager, etc.<\/p>\n<figure style=\"width: 2014px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/service-google-quic.png\" alt=\"Google QUIC Service\" width=\"2014\" height=\"838\"><figcaption class=\"wp-caption-text\">Service Google QUIC<\/figcaption><\/figure>\n<p>Cloudflare a r\u00e9cemment publi\u00e9 <a href=\"https:\/\/blog.cloudflare.com\/http-3-from-root-to-tip\/\" target=\"_blank\" rel=\"noopener noreferrer\">une mise \u00e0 jour tr\u00e8s compl\u00e8te<\/a> sur les progr\u00e8s de la normalisation.<\/p>\n<p>Bien que le protocole UDP offre certains avantages inh\u00e9rents au QUIC et au HTTP\/3, il comporte aussi certains d\u00e9fis.<\/p>\n<p>TCP est le protocole courant depuis des ann\u00e9es, alors que UDP ne l&rsquo;est pas, de sorte que les syst\u00e8mes d&rsquo;exploitation et la pile logicielle n&rsquo;est g\u00e9n\u00e9ralement pas aussi optimis\u00e9e. Par cons\u00e9quent, il y a beaucoup plus de charge\/besoins CPU avec QUIC, selon certaines estimations, deux fois plus qu&rsquo;avec HTTP\/2.<\/p>\n<p>Les optimisations vont en profondeur jusqu&rsquo;au noyau des syst\u00e8mes d&rsquo;exploitation et aux <a href=\"https:\/\/electronics.stackexchange.com\/questions\/246184\/how-does-the-tcp-ip-stack-interact-with-wifi-components\" target=\"_blank\" rel=\"noopener noreferrer\">diff\u00e9rents routeurs et micrologiciels des appareils<\/a>. Ce <a href=\"https:\/\/access.redhat.com\/sites\/default\/files\/attachments\/20150325_network_performance_tuning.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">guide Red Hat Tuning<\/a> peut apporter plus de lumi\u00e8re sur le sujet pour ceux qui sont plus enclins sur le plan technique.<\/p>\n<p>Nous pourrions dire que QUIC tente de r\u00e9inventer les fonctionnalit\u00e9s TCP en plus d&rsquo;un protocole plus minimal et plus flexible.<\/p>\n<p>Les connexions QUIC, que nous avons mentionn\u00e9es plus haut, combinent le TLS et les poign\u00e9es de main de transport. Une fois \u00e9tablis, ils sont identifi\u00e9s par des CIDs uniques (ID de connexion). Ces IDs persistent \u00e0 travers les changements d&rsquo;IP et peuvent aider \u00e0 s\u00e9curiser les t\u00e9l\u00e9chargements ininterrompus sur, par exemple, un passage de la 4G vers le WiFi. Cela est d&rsquo;autant plus important que le trafic Internet est de plus en plus important sur les appareils mobiles. On peut se demander si cet \u00e9l\u00e9ment est con\u00e7u par Google pour faciliter un meilleur suivi des utilisateurs entre les diff\u00e9rentes connexions et les diff\u00e9rents fournisseurs d&rsquo;acc\u00e8s \u00e0 Internet.<\/p>\n<p>Le protocole TLS est obligatoire et vise \u00e0 emp\u00eacher les p\u00e9riph\u00e9riques situ\u00e9s au milieu d\u2019alt\u00e9rer ou de snifer le trafic. C&rsquo;est pourquoi il n&rsquo;est pas rare de voir des fournisseurs de pare-feu comme Cisco voir le protocole UDP comme un probl\u00e8me, et de fournir des moyens de le d\u00e9sactiver. Il est plus difficile pour les interm\u00e9diaires d&rsquo;inspecter et de superviser ou de filtrer le trafic QUIC.<\/p>\n<p>Les flux QUIC sont envoy\u00e9s via des connexions QUIC, unidirectionnelles ou bidirectionnelles. Les flux ont des IDs qui identifient l&rsquo;initiateur et indiquent si le flux est unidirectionnel ou bidirectionnel, et servent \u00e9galement au contr\u00f4le du d\u00e9bit dans le flux.<\/p>\n<p>Alors que QUIC est un protocole de couche de transport, HTTP est la couche sup\u00e9rieure, un protocole de couche d&rsquo;application, ou protocole d&rsquo;application.<\/p>\n<p>Comme la r\u00e9trocompatibilit\u00e9 est de la plus haute importance, l&rsquo;IETF a encourag\u00e9 la mise en \u0153uvre de HTTP\/3 en incluant l&rsquo;ancienne version (HTT1 ou HTTP\/2) dans la r\u00e9ponse. Il comprendra un en-t\u00eate qui informe le client que HTTP\/3 est disponible, ainsi que des informations sur le port\/h\u00f4te, comme d\u00e9crit dans la <a href=\"https:\/\/tools.ietf.org\/html\/rfc7838\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 7838<\/a>.<\/p>\n<p>C&rsquo;est diff\u00e9rent de HTTP\/2, dans lequel le transport peut \u00eatre n\u00e9goci\u00e9 dans le cadre de la prise de <a href=\"https:\/\/staging.kinsta.site\/fr\/base-de-connaissances\/tls-vs-ssl\/\">contact TLS<\/a>. Mais comme l&rsquo;IETF a pratiquement adopt\u00e9 le protocole HTTP\/3 bas\u00e9 sur QUIC comme norme suivante, nous pouvons nous attendre \u00e0 ce que les clients Web anticipent de plus en plus le support de HTTP\/3. Il est possible pour les clients de mettre en cache les donn\u00e9es des connexions HTTP\/3 pr\u00e9c\u00e9dentes, et de se connecter directement (zero-round-trip, ou 0-RTT) lors de visites ult\u00e9rieures sur le m\u00eame h\u00e9bergeur.<\/p>\n<h2>R\u00e9sum\u00e9<\/h2>\n<p>Il y a ceux qui pensent qu&rsquo;avec l&rsquo;adoption incompl\u00e8te de la norme HTTP\/2, il est peut-\u00eatre trop t\u00f4t pour faire pression en faveur de HTTP\/3. C&rsquo;est un point valable, mais, comme nous l&rsquo;avons mentionn\u00e9, ce protocole a d\u00e9j\u00e0 fait l&rsquo;objet d&rsquo;essais et de mises en \u0153uvre \u00e0 grande \u00e9chelle. Google a commenc\u00e9 \u00e0 le tester d\u00e8s <a href=\"https:\/\/www.theregister.co.uk\/2015\/04\/17\/google_quic_test_results\/\" target=\"_blank\" rel=\"noopener noreferrer\">2015<\/a>, ainsi que Facebook en <a href=\"https:\/\/code.fb.com\/networking-traffic\/building-zero-protocol-for-fast-secure-mobile-connections\/\" target=\"_blank\" rel=\"noopener noreferrer\">2017<\/a>.<\/p>\n<p>En 2026, les principaux navigateurs comme Google Chrome et Brave prennent en charge HTTP\/3. Sur le plan de l&rsquo;infrastructure, des serveurs web comme <a href=\"https:\/\/docs.litespeedtech.com\/cp\/cpanel\/quic-http3\/\">Litespeed<\/a> et <a href=\"https:\/\/www.nginx.com\/blog\/introducing-technology-preview-nginx-support-for-quic-http-3\/\">Nginx<\/a> disposent tous deux d&rsquo;impl\u00e9mentations fonctionnelles de HTTP\/3, tandis que des fournisseurs de r\u00e9seaux comme Cloudflare ont d\u00e9j\u00e0 d\u00e9ploy\u00e9 un <a href=\"https:\/\/blog.cloudflare.com\/http3-the-past-present-and-future\/\">support complet de HTTP\/3<\/a>.<\/p>\n<p><span style=\"vertical-align: inherit\"><span style=\"vertical-align: inherit\">Currently, HTTP\/3 is still in the Internet Draft phase, and the latest revision is due to expire in August 2021. This year will be exciting, as we can expect to see major software vendors implementing the new standard.<\/span><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR In November 2018, the Internet Engineering Task Force (IETF) met in Bangkok and a new Internet project was adopted. The QUIC transport protocol, the successor &#8230;<\/p>\n","protected":false},"author":93,"featured_media":25281,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kinsta_gated_content":false,"_kinsta_gated_content_redirect":"","footnotes":""},"tags":[136,135],"topic":[],"class_list":["post-25269","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","tag-http3","tag-quic"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v17.1.2 (Yoast SEO v25.8) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?<\/title>\n<meta name=\"description\" content=\"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?\" \/>\n<meta property=\"og:description\" content=\"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/\" \/>\n<meta property=\"og:site_name\" content=\"Kinsta\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/kinstafrance\/\" \/>\n<meta property=\"article:published_time\" content=\"2019-04-06T03:57:55+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-04-06T13:19:48+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1460\" \/>\n\t<meta property=\"og:image:height\" content=\"730\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Tonino Jankov\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?\" \/>\n<meta name=\"twitter:description\" content=\"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg\" \/>\n<meta name=\"twitter:creator\" content=\"@t_jankov\" \/>\n<meta name=\"twitter:site\" content=\"@kinsta_fr\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Tonino Jankov\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/\"},\"author\":{\"name\":\"Tonino Jankov\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#\/schema\/person\/ad4393a59128f5f8f3bfd2737054c61c\"},\"headline\":\"Qu\u2019est-ce que HTTP\/3 &#8211; Informations sur le nouveau protocole UDP rapide ?\",\"datePublished\":\"2019-04-06T03:57:55+00:00\",\"dateModified\":\"2022-04-06T13:19:48+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/\"},\"wordCount\":4027,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#organization\"},\"image\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg\",\"keywords\":[\"http3\",\"quic\"],\"articleSection\":[\"Tutoriels sur la performance WordPress\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/\",\"url\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/\",\"name\":\"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?\",\"isPartOf\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg\",\"datePublished\":\"2019-04-06T03:57:55+00:00\",\"dateModified\":\"2022-04-06T13:19:48+00:00\",\"description\":\"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.\",\"breadcrumb\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage\",\"url\":\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg\",\"contentUrl\":\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg\",\"width\":1460,\"height\":730,\"caption\":\"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/staging.kinsta.site\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Qu\u2019est-ce que HTTP\/3 &#8211; Informations sur le nouveau protocole UDP rapide ?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#website\",\"url\":\"https:\/\/staging.kinsta.site\/fr\/\",\"name\":\"Kinsta\",\"description\":\"Solutions d&#039;h\u00e9bergement premium, rapides et s\u00e9curis\u00e9es\",\"publisher\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/staging.kinsta.site\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#organization\",\"name\":\"Kinsta\",\"url\":\"https:\/\/staging.kinsta.site\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2018\/05\/kinsta.png\",\"contentUrl\":\"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2018\/05\/kinsta.png\",\"width\":580,\"height\":580,\"caption\":\"Kinsta\"},\"image\":{\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/kinstafrance\/\",\"https:\/\/x.com\/kinsta_fr\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#\/schema\/person\/ad4393a59128f5f8f3bfd2737054c61c\",\"name\":\"Tonino Jankov\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/staging.kinsta.site\/fr\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/18b28c81507387b395f0ce784f80fb4f3ff8a850399a71494c536046870c65ce?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/18b28c81507387b395f0ce784f80fb4f3ff8a850399a71494c536046870c65ce?s=96&d=mm&r=g\",\"caption\":\"Tonino Jankov\"},\"description\":\"Tonino is an entrepreneur, Linux &amp; OSS enthusiast, developer, and tech educator. He has over ten years of experience in development and has been in the blockchain space for 3+ years. When he's not coding, he writes for SitePoint and Alibaba Cloud, binge-watches the newest works of fiction on Netflix, and explores new travel destinations.\",\"sameAs\":[\"https:\/\/x.com\/t_jankov\"],\"url\":\"https:\/\/staging.kinsta.site\/fr\/blog\/author\/toninojankov\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?","description":"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/","og_locale":"fr_FR","og_type":"article","og_title":"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?","og_description":"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.","og_url":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/","og_site_name":"Kinsta","article_publisher":"https:\/\/www.facebook.com\/kinstafrance\/","article_published_time":"2019-04-06T03:57:55+00:00","article_modified_time":"2022-04-06T13:19:48+00:00","og_image":[{"width":1460,"height":730,"url":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg","type":"image\/jpeg"}],"author":"Tonino Jankov","twitter_card":"summary_large_image","twitter_title":"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?","twitter_description":"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.","twitter_image":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg","twitter_creator":"@t_jankov","twitter_site":"@kinsta_fr","twitter_misc":{"\u00c9crit par":"Tonino Jankov","Dur\u00e9e de lecture estim\u00e9e":"20 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#article","isPartOf":{"@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/"},"author":{"name":"Tonino Jankov","@id":"https:\/\/staging.kinsta.site\/fr\/#\/schema\/person\/ad4393a59128f5f8f3bfd2737054c61c"},"headline":"Qu\u2019est-ce que HTTP\/3 &#8211; Informations sur le nouveau protocole UDP rapide ?","datePublished":"2019-04-06T03:57:55+00:00","dateModified":"2022-04-06T13:19:48+00:00","mainEntityOfPage":{"@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/"},"wordCount":4027,"commentCount":0,"publisher":{"@id":"https:\/\/staging.kinsta.site\/fr\/#organization"},"image":{"@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage"},"thumbnailUrl":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg","keywords":["http3","quic"],"articleSection":["Tutoriels sur la performance WordPress"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/","url":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/","name":"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?","isPartOf":{"@id":"https:\/\/staging.kinsta.site\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage"},"image":{"@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage"},"thumbnailUrl":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg","datePublished":"2019-04-06T03:57:55+00:00","dateModified":"2022-04-06T13:19:48+00:00","description":"HTTP\/3 est la troisi\u00e8me version du protocole HTTP (Hypertext Transfer Protocol), anciennement HTTP over-QUIC. Voyez comment \u00e7a acc\u00e9l\u00e8re le web.","breadcrumb":{"@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/staging.kinsta.site\/fr\/blog\/http3\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#primaryimage","url":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg","contentUrl":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2019\/03\/http3-1.jpg","width":1460,"height":730,"caption":"Qu\u2019est-ce que HTTP\/3 - Informations sur le nouveau protocole UDP rapide ?"},{"@type":"BreadcrumbList","@id":"https:\/\/staging.kinsta.site\/fr\/blog\/http3\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/staging.kinsta.site\/fr\/"},{"@type":"ListItem","position":2,"name":"Qu\u2019est-ce que HTTP\/3 &#8211; Informations sur le nouveau protocole UDP rapide ?"}]},{"@type":"WebSite","@id":"https:\/\/staging.kinsta.site\/fr\/#website","url":"https:\/\/staging.kinsta.site\/fr\/","name":"Kinsta","description":"Solutions d&#039;h\u00e9bergement premium, rapides et s\u00e9curis\u00e9es","publisher":{"@id":"https:\/\/staging.kinsta.site\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/staging.kinsta.site\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/staging.kinsta.site\/fr\/#organization","name":"Kinsta","url":"https:\/\/staging.kinsta.site\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/staging.kinsta.site\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2018\/05\/kinsta.png","contentUrl":"https:\/\/staging.kinsta.site\/fr\/wp-content\/uploads\/sites\/4\/2018\/05\/kinsta.png","width":580,"height":580,"caption":"Kinsta"},"image":{"@id":"https:\/\/staging.kinsta.site\/fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/kinstafrance\/","https:\/\/x.com\/kinsta_fr"]},{"@type":"Person","@id":"https:\/\/staging.kinsta.site\/fr\/#\/schema\/person\/ad4393a59128f5f8f3bfd2737054c61c","name":"Tonino Jankov","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/staging.kinsta.site\/fr\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/18b28c81507387b395f0ce784f80fb4f3ff8a850399a71494c536046870c65ce?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/18b28c81507387b395f0ce784f80fb4f3ff8a850399a71494c536046870c65ce?s=96&d=mm&r=g","caption":"Tonino Jankov"},"description":"Tonino is an entrepreneur, Linux &amp; OSS enthusiast, developer, and tech educator. He has over ten years of experience in development and has been in the blockchain space for 3+ years. When he's not coding, he writes for SitePoint and Alibaba Cloud, binge-watches the newest works of fiction on Netflix, and explores new travel destinations.","sameAs":["https:\/\/x.com\/t_jankov"],"url":"https:\/\/staging.kinsta.site\/fr\/blog\/author\/toninojankov\/"}]}},"acf":[],"_links":{"self":[{"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/posts\/25269","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/users\/93"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/comments?post=25269"}],"version-history":[{"count":16,"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/posts\/25269\/revisions"}],"predecessor-version":[{"id":55172,"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/posts\/25269\/revisions\/55172"}],"alternate":[{"embeddable":true,"hreflang":"en","title":"English","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/en"},{"embeddable":true,"hreflang":"fr","title":"French","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/fr"},{"embeddable":true,"hreflang":"it","title":"Italian","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/it"},{"embeddable":true,"hreflang":"es","title":"Spanish","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/es"},{"embeddable":true,"hreflang":"nl","title":"Dutch","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/nl"},{"embeddable":true,"hreflang":"da","title":"Danish","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/dk"},{"embeddable":true,"hreflang":"sv","title":"Swedish","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/se"},{"embeddable":true,"hreflang":"de","title":"German","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/de"},{"embeddable":true,"hreflang":"pt","title":"Portuguese","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/pt"},{"embeddable":true,"hreflang":"ja","title":"Japanese","href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/translations\/jp"},{"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/kinsta\/v1\/posts\/25269\/tree"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/media\/25281"}],"wp:attachment":[{"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/media?parent=25269"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/tags?post=25269"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/staging.kinsta.site\/fr\/wp-json\/wp\/v2\/topic?post=25269"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}