# QUIC Published articles for QUIC. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ktor 3.6.0 Is Now Available! DevFeed: [Ktor 3.6.0 Is Now Available!]() Original publisher: [Read original article]() Author: Simon Vergauwen Published: 2026-09-18T10:45:56Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [Ktor](), [Kotlin](), [Netty](), [Authentication](), [HTTP](), [openid](), [multiplatform](), [clients](), [Routing (disambiguation)]() Tags: [authentication](), [clients](), [http](), [http-3](), [kotlin](), [kotlin-multiplatform](), [ktor](), [news](), [openid](), [quic](), [release](), [releases](), [routing](), [server]() ### AI overview Ktor 3.6.0 introduces experimental typed authentication with OpenID Connect support and HTTP/3 over QUIC for the Netty engine. The release also improves routing, request handling, and Kotlin Multiplatform client defaults. ### Source excerpt Ktor 3.6.0 is here! This release is full of new experimental features, including typed authentication capabilities with specialized support for OpenID Connect and HTTP/3 support for the Netty engine. There are also a few quality-of-life improvements for routing and request handling, more convenient defaults for Kotlin Multiplatform clients, and more. Check out What's new in [...] ## RFC 9852: New Protocols Using TLS Must Require TLS 1.3 DevFeed: [RFC 9852: New Protocols Using TLS Must Require TLS 1.3]() Original publisher: [Read original article]() Published: 2026-07-17T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [TLS (Transport Layer Security)](), [protocols](), [Internet Engineering Task Force (IETF)](), [QUIC]() Tags: [ietf](), [internet](), [protocols](), [quic](), [rfc](), [tls](), [version]() ### AI overview This French article explains RFC 9852, which strongly advises designers of new cryptographic network protocols to require TLS 1.3 or later. It contrasts TLS 1.3 with TLS 1.2, discusses configuration and security weaknesses in TLS 1.2, notes QUIC's TLS 1.3 requirement, and mentions implications for post-quantum cryptography. ### Source excerpt Si vous concevez des protocoles réseau utilisant la cryptographie, vous utiliserez souvent TLS. Dans ce cas, pour un nouveau protocole, n'ayant pas à gérer l'existant, l'IETF vous conseille fortement, dans ce RFC, d'exiger dans la définition du protocole qu'il faut au moins la version 1.3 de TLS. ## Les limites de la métrique " nombre d'octets " sur les réseaux informatiques DevFeed: [Les limites de la métrique " nombre d'octets " sur les réseaux informatiques]() Original publisher: [Read original article]() Published: 2026-07-17T00:00:00Z Content type: opinion Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [Internet](), [QUIC]() Tags: [akamai](), [amazon](), [google](), [internet](), [meta](), [netflix](), [quic](), [rfc](), [tcp]() ### AI overview This article examines the limitations of using byte counts to compare Internet traffic. It argues that byte volume can obscure strategic importance and considers alternatives such as flow counts and economic value, including for comparisons between public and private peering. ### Source excerpt La présentation, le 16 juillet 2026, du rapport annuel de l'ARCEP sur l'état de l'Internet en France (https://www.arcep.fr/actualites/actualites-et-communiques/detail/n/rapport-annuel-tome3-160726.html) a été l'occasion de se poser la question : quand on compare quantitativement des choses sur l'Internet, par exemple l'appairage public et le transit, on utilise presque toujours comme métrique le nombre d'octets. Est-ce une bonne idée ? ## Workshop Basel day two DevFeed: [Workshop Basel day two]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-15T20:07:14Z Content type: article Language: en Sources: [Daniel Stenberg]() Topics: [HTTP](), [servers](), [Artificial Intelligence](), [Git](), [Open Source]() Tags: [ai](), [git](), [http](), [http-3](), [http-server](), [http-workshop](), [measurement](), [network](), [open-source](), [performance](), [quic](), [tests](), [web]() ### AI overview A report from the second day of a Basel workshop covering AI's influence on HTTP implementation, HTTP/2 measurements from large-scale web crawls, HTTP/1.1 behavior testing, request-smuggling tests, server performance measurement, and efforts to increase HTTP/3 and QUIC usage. ### Source excerpt If you missed it. I already described day one. Caffeinated and ready, we all gathered in the same spacious room as yesterday, but seated in new places as "suggested" by our captain. Some of us even remembered to move over the name tags we wrote yesterday to our new seats. No time was wasted on ... Continue reading Workshop Basel day two -> ## Workshop Basel day one DevFeed: [Workshop Basel day one]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-14T20:25:28Z Content type: article Language: en Sources: [Daniel Stenberg]() Topics: [HTTP](), [networking](), [interoperability]() Tags: [http](), [http-workshop](), [interoperability](), [network](), [networking](), [quic](), [switzerland](), [web]() ### AI overview A report from the first day of the seventh HTTP workshop in Basel, Switzerland, covering discussions about extending REST and HTTP for state synchronization, Last-Modified header usage, HTTP usage data, and interoperability challenges. ### Source excerpt On this hot summer's day in Basel, Switzerland, the seventh HTTP workshop started. These events tend to work roughly the same way and the people in the room are also to large extent familiar and known since previous editions. Forty people in a meeting room, where we take turns in doing short talks on HTTP ... Continue reading Workshop Basel day one -> ## RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3 DevFeed: [RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3]() Original publisher: [Read original article]() Published: 2026-07-12T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [TLS (Transport Layer Security)](), [Protocol (disambiguation)](), [Security](), [version](), [Internet Engineering Task Force (IETF)](), [client](), [Internet](), [QUIC]() Tags: [client](), [ietf](), [internet](), [protocol](), [quic](), [rfc](), [security](), [tls](), [version]() ### AI overview This French article explains RFC 9846, which updates the TLS 1.3 standard. It describes TLS as a mechanism for secure client-server communication over untrusted networks, including its relationship with TCP and QUIC, and introduces the protocol's complexity and components. ### Source excerpt Ce RFC met à jour la norme de la version 1.3 du protocole de cryptographie TLS. Il n'y a pas de grand changement par rapport à son prédécesseur, le RFC 8446. ## Worth Reading: BGP Route Leaks, TCP Latency, and Datacenter Packet-Processing Energy DevFeed: [Worth Reading: BGP Route Leaks, TCP Latency, and Datacenter Packet-Processing Energy]() Original publisher: [Read original article]() Author: Russ Published: 2026-04-29T19:44:35Z Content type: article Language: en Sources: [rule 11 reader]() Topics: [BGP](), [Networks](), [datacenter](), [systems](), [Internet]() Tags: [bgp](), [datacenter](), [internet](), [networks](), [privacy](), [quic](), [systems](), [tcp](), [technical](), [worth-reading]() ### AI overview This developer reading roundup covers BGP route leaks that may be brief artifacts of normal convergence, the effects of long round-trip times on TCP, the energy costs of host-side packet processing in high-speed datacenter networks, changing satellite internet capabilities, orbital models, and what unsolicited QUIC traffic can reveal about deployments and metadata privacy. ### Source excerpt Many BGP route leaks reported by automated detection systems are actually brief, low-impact artifacts of normal BGP convergence. Long round-trip times have serious consequences for protocols like TCP, which rely on a steady stream of acknowledgements (ACKs) to manage sending rates, estimate delay, and trigger retransmissions. As datacenter networks evolve toward ultra-high-speed links, the energy footprint of host-side packet processing grows increasingly significant. The old perception of satellite internet as slow, expensive, and marginal is increasingly outdated. Today's market includes multiple orbital models, each with distinct technical and operational characteristics. What can we learn about QUIC deployments just by listening to unsolicited QUIC traffic? This question becomes specifically exciting since QUIC aims to enhance privacy by obfuscating metadata. ## How TCP Handshake Works DevFeed: [How TCP Handshake Works]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-31T08:17:52Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Handshake](), [client](), [servers]() Tags: [client](), [communication](), [http-3](), [quic](), [sequence](), [server](), [tcp](), [tcp-handshake]() ### AI overview A tutorial explaining the TCP three-way handshake. It describes how a client sends SYN, a server responds with SYN-ACK, and the client completes the connection with ACK, including the role of initial sequence numbers and control flags. ### Source excerpt The 3 step process ## Post-Quantum Cryptography Proof of Concept Implementations DevFeed: [Post-Quantum Cryptography Proof of Concept Implementations]() Original publisher: [Read original article]() Published: 2025-07-20T21:35:33Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [Post-Quantum](), [Post-quantum cryptography](), [QUIC](), [TLS (Transport Layer Security)](), [Server](), [client]() Tags: [client](), [cryptography](), [language](), [post-quantum](), [post-quantum-cryptography](), [quantum](), [quic](), [server](), [tls]() ### AI overview The article presents a few QUIC post-quantum cryptography TLS server implementations intended to help verify client and language capabilities. ### Source excerpt A few quic PQC TLS server implekentations to help you verify client and language capabilities. ## How Browsers Choose Between HTTPS over TCP and QUIC DevFeed: [How Browsers Choose Between HTTPS over TCP and QUIC]() Original publisher: [Read original article]() Published: 2025-06-03T06:30:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [browser](), [Web](), [servers](), [Protocol (disambiguation)]() Tags: [browser](), [distributed](), [protocol](), [quic](), [server](), [tcp](), [trust](), [worth-reading]() ### AI overview The article discusses how browsers determine whether a web server supports QUIC and choose between HTTPS over TCP and QUIC. It notes that browser vendors do not trust distributed database data about server capabilities and instead use a happy eyeballs-like protocol. ### Source excerpt Jan Schaumann published an interesting blog post describing the circuitous journey a browser might take to figure out that it can use QUIC with a web server. Now, if only there were a record in a distributed database telling the browser what the web server supports. Oh, wait... Not surprisingly, browser vendors don't trust that data and have implemented a happy eyeballs-like protocol to decide between HTTPS over TCP and QUIC. ## HTTP/3 adoption is widespread in browsers and CDNs but limited in open-source tools DevFeed: [HTTP/3 adoption is widespread in browsers and CDNs but limited in open-source tools]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2025-03-12T16:00:00Z Content type: opinion Language: en Sources: [HTTP Toolkit]() Topics: [HTTP3](), [networking](), [Protocol (disambiguation)](), [Open Source]() Tags: [browsers](), [http](), [http-3](), [http3](), [networking](), [open-source](), [quic](), [standards]() ### AI overview This article examines the contrast between HTTP/3's widespread browser and CDN adoption and its limited support in major programming-language libraries, servers, Android networking, and Kubernetes tooling. It argues that HTTP/3 rollout beyond browsers and large CDNs remains at an early stage. ### Source excerpt HTTP/3 has been in development since at least 2016, while QUIC (the protocol beneath it) was first introduced by Google way back in 2013. Both are now standardized, supported in 95% of users' browsers, already used in 32% of HTTP requests to Cloudflare, and support is advertised by 35% of websites (through alt-svc or DNS) in the HTTP Archive dataset. We've developed a totally new version of HTTP, and we're on track to migrate more than 1/3 of web traffic to it already! This is astonishing progress. At the same time, neither QUIC nor HTTP/3 are included in the standard libraries of any major languages including Node.js, Go, Rust, Python or Ruby. Curl recently gained support but it's experimental and disabled in most distributions. There are a rare few external libraries for some languages, but all are experimental and/or independent of other core networking APIs. Despite mobile networking being a key use case for HTTP/3, Android's most popular HTTP library has no support. Popular servers like Nginx have only experimental support, disabled by default, Apache has no support or published plan for support, and Ingress-Nginx (arguably the most popular Kubernetes reverse proxy) has dropped all plans for HTTP/3 support punting everything to a totally new (as yet unreleased) successor project instead. Really it's hard to point to any popular open-source tools that fully support HTTP/3: rollout has barely even started. This seems contradictory. What's going on? I'm going to assume a basic familiarity with the differences between HTTP/1.1 (et al), HTTP/2 and HTTP/3 here. If you're looking for more context, http2-explained and http3-explained from Daniel Stenberg (founder & lead developer of curl) is an excellent guide. Why do we need more than HTTP/1.1? Let's step back briefly. Why does this matter? Who cares about whether HTTP/3 is being rolled out successfully or not? If browser traffic and the big CDNs support HTTP/3, do we even need it in other client or server implementat ## Rock and Rollback: Realtime multiplayer in the browser, with rust and bevy DevFeed: [Rock and Rollback: Realtime multiplayer in the browser, with rust and bevy]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2024-12-08T06:00:00Z Content type: tutorial Language: en Sources: [Richard Jones]() Topics: [browser](), [browser-game](), [realtime](), [Bevy](), [Rust](), [QUIC](), [WebRTC](), [HTTP](), [Streaming]() Tags: [bevy](), [bevygap](), [browser](), [gamedev](), [http-3](), [multiplayer](), [netcode](), [quic](), [realtime](), [rust](), [snapshots](), [udp](), [webrtc]() ### AI overview This article discusses building a realtime multiplayer browser game with Rust and Bevy. It explains why TCP can delay updates, considers WebRTC and WebTransport over HTTP/3 and QUIC for unreliable data channels, and introduces snapshot interpolation as a multiplayer networking model. ### Source excerpt How hard it is to build a realtime multiplayer browser game? Like asteroids, but multiplayer. Retro vibes with modern netcode 🚀. ## Chrome enables Kyber post-quantum key exchange by default for TLS 1.3 and QUIC DevFeed: [Chrome enables Kyber post-quantum key exchange by default for TLS 1.3 and QUIC]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-05-23T17:19:00Z Content type: release Language: en Sources: [Chromium Blog]() Topics: [Post-quantum cryptography](), [Chrome](), [chrome security](), [Google](), [TLS (Transport Layer Security)](), [Security]() Tags: [chrome](), [chrome-security](), [google](), [none](), [post-quantum-cryptography](), [quic](), [security](), [tls]() ### AI overview Google announces that Chrome 124 enables the latest Kyber draft specification by default for TLS 1.3 and QUIC on desktop platforms. The rollout exposed existing TLS middlebox bugs, and Chrome provides a temporary enterprise opt-out policy while fixes are deployed. ### Source excerpt Google and many other organizations, such as NIST, IETF, and NSA, believe that migrating to post-quantum cryptography is important due to the large risk posed by a cryptographically-relevant quantum computer (CRQC). In August, we posted about how Chrome Security is working to protect users from the risk of future quantum computers by leveraging a new form of hybrid post-quantum cryptographic key exchange, Kyber (ML-KEM)1. We're happy to announce that we have enabled the latest Kyber draft specification by default for TLS 1.3 and QUIC on all desktop Chrome platforms as of Chrome 124.2 This rollout revealed a number of previously-existing bugs in several TLS middlebox products. To assist with the deployment of fixes, Chrome is offering a temporary enterprise policy to opt-out. Launching opportunistic quantum-resistant key exchange is part of Google's broader strategy to prioritize deploying post-quantum cryptography in systems today that are at risk if an adversary has access to a quantum computer in the future. We believe that it's important to inform standards with real-world experience, by implementing drafts and iterating based on feedback from implementers and early adopters. This iterative approach was a key part of developing QUIC and TLS 1.3. It's part of why we're launching this draft version of Kyber, and it informs our future plans for post-quantum cryptography. Chrome's post-quantum strategy prioritizes quantum-resistant key exchange in HTTPS, and increased agility in certificates from the Web PKI. While PKI agility may appear somewhat unrelated, its absence has contributed to significant delays in past cryptographic transitions and will continue to do so until we find a viable solution in this space. A more agile Web PKI is required to enable a secure and reliable transition to post-quantum cryptography on the web. To understand this, let's take a look at HTTPS and the current state of post-quantum cryptography. In the context of HTTPS, cryptography is pr ## Supabase Launch Week: pg\_graphql, CDN, and Network Performance Updates DevFeed: [Supabase Launch Week: pg\_graphql, CDN, and Network Performance Updates]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2021-12-03T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [GraphQL](), [PostgreSQL](), [HTTP](), [QUIC](), [Compression](), [TLS (Transport Layer Security)]() Tags: [compression](), [graphql](), [http](), [http-3](), [launch](), [open-source](), [postgresql](), [quic](), [release](), [tls]() ### AI overview Supabase announces pg_graphql, a native PostgreSQL extension for GraphQL, launches a CDN for all projects, and describes performance improvements involving TLS 1.3, HTTP/3, Brotli compression, and API reliability. ### Source excerpt It's never just one more thing! ## Node.js 17.0.0 (Current) DevFeed: [Node.js 17.0.0 (Current)]() Original publisher: [Read original article]() Published: 2021-10-19T15:42:09Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [V8](), [Open Source](), [cross-platform](), [servers](), [Web](), [Command-line interface]() Tags: [cross-platform](), [features](), [fips](), [javascript](), [msvc](), [node-js](), [npm](), [open-source](), [quic]() ### AI overview Node.js 17.0.0 is a current release that introduces OpenSSL 3.0 with QUIC and renewed FIPS support, updates the V8 JavaScript engine to 9.5, upgrades npm to 8.1.0, and adds several runtime, stream, filesystem, and build changes. The release also includes deprecations and potentially breaking changes affecting DNS behavior, module resolution patterns, cryptographic algorithms, and key sizes. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts.