Tagged articles
HTTP/3
68 articles · Page 1 of 1

java1234Oct 24, 2026 · Backend Development
This article explores Jetty 12's architectural rewrite decoupling core from Servlet, and details Jetty 12.1's new features including Jakarta EE 11 support, a pluggable compression layer with gzip, Brotli, and Zstandard, a unified deployer, multi-authenticator flexibility, and a showcase combining virtual threads, EE11 servlets, and multi-algorithm compression.
CompressionEmbedded ServerHTTP/3
0 likes · 25 min read


TonyBaiOct 20, 2026 · Backend Development
Go proposal #77441 adds Server.HandleRequest to net/http, exposing internal request-processing middleware (OPTIONS *, DefaultServeMux fallback, panic recovery) so HTTP/3 and other protocol implementations can reuse standard library behavior without code duplication, while also enabling full-server integration testing.
API DesignGoHTTP/3
0 likes · 18 min read


java1234Oct 15, 2026 · Backend Development
This article explores Netty 4.2's major changes including the new adaptive memory allocator, composable MultiThreadIoEventLoopGroup with IoHandlerFactory, official io_uring transport support, ManualIoEventLoop for custom event-loop driving, QUIC/HTTP/3 graduation, and default client TLS hostname verification.
AdaptiveByteBufAllocatorByteBufEventLoop
0 likes · 17 min read

Java 26 introduces HTTP/3 support in its HTTP Client API, enabling developers to use QUIC-based connections with minimal code changes, including three protocol discovery modes and automatic fallback to HTTP/2 or HTTP/1.1 when servers lack HTTP/3 support.
HTTP Client APIHTTP/3Java 26
0 likes · 8 min read

The article analyzes why Cloudflare only supports HTTP/3 on the client‑to‑edge path, detailing the protocol split, CPU and hardware offload costs, UDP restrictions, and why HTTP/3 remains viable despite not being used for origin fetches.
CDNCloudflareHTTP/3
0 likes · 9 min read

This article explores major Java core library enhancements from versions 11 to 26, including the HTTP Client with HTTP/3 support, FFM API for safe native interop replacing JNI, Stream Gatherers for custom intermediate operations like sliding windows, SequencedCollection for unified ordered collections, KDF and post-quantum cryptography, plus numerous String, IO, and random-number improvements that reduce third-party dependencies.
FFM APIHTTP ClientHTTP/3
0 likes · 20 min read

TrueAsync Server is a high‑performance HTTP/1.1, HTTP/2 and HTTP/3 server written in C that embeds directly into the PHP process, runs entirely on a single thread, eliminates inter‑thread communication, supports multi‑protocol on one port, and offers a suite of low‑level optimizations and a clear API for developers.
BackendC++HTTP/3
0 likes · 17 min read

Version 1.3.14 of Bun was released on May 13, featuring a massive Rust rewrite that has already passed tests on all major platforms, closed around 200 issues, introduced built‑in image processing, HTTP/3 support, and dramatically reduced binary size, while the migration—driven by AI agents—produced 960 k lines of Rust with 13,044 unsafe blocks, signaling a potential shift away from Zig.
AIBunHTTP/3
0 likes · 15 min read

The article examines why Java 26 has sparked intense discussion—not for flashy syntax but for concrete upgrades like HTTP/3, performance tweaks, and GC improvements—guiding developers on when and how to adopt the new version responsibly.
AOT cachingGC optimizationHTTP/3
0 likes · 8 min read


21CTOApr 13, 2026 · Industry Insights
The article analyzes why HTTP/3, built on QUIC over UDP, can outperform HTTP/2 in lossy or mobile networks by eliminating TCP's head‑of‑line blocking, offering faster handshakes, seamless connection migration, and better congestion control, while also outlining scenarios where HTTP/2 remains preferable.
HTTP/3QUICTCP
0 likes · 10 min read

The article explains how Java’s six‑month release cadence has led to JDK 26’s major upgrades—including HTTP/3, Structured Concurrency, stronger final‑field immutability, AOT object caching, G1 GC enhancements, Lazy Constants, pattern‑matching extensions, Vector API and PEM support—showing the performance, latency and security gains developers can unlock by moving beyond Java 8.
G1 GCHTTP/3JDK 26
0 likes · 9 min read

Oracle’s JDK 26, a non‑LTS release, delivers dramatic gains—15% higher G1 GC throughput, up to 50% lower latency, 40‑60% memory reduction via Valhalla value classes, native HTTP/3 support, AOT cache for all GCs, and enhanced security—offering developers faster startup, lower costs, and safer code.
G1 GCHTTP/3JDK 26
0 likes · 10 min read

JDK 26, released on March 17, 2026, introduces structured concurrency, native HTTP/3, primitive‑type pattern matching, lazy constants, G1 GC sync improvements, AOT object caching, final‑field reflection limits and post‑quantum encryption, delivering up to 30% performance gains, 40% thread‑utilisation, and up to 70% code‑size reduction without requiring code changes or new dependencies.
G1 GCHTTP/3JDK 26
0 likes · 11 min read

The article provides a comprehensive analysis of Go 1.26’s major enhancements—including stable Arena memory management, expanded generics in the standard library, native HTTP/3 support, integrated security checks, performance benchmarks, and practical upgrade recommendations for production environments.
ArenaGenericsGo
0 likes · 9 min read

This article examines how HTTP/3’s Connection ID decouples a connection from its IP/port tuple, enabling transparent network migration for gRPC over QUIC, and explores the practical limits of 0‑RTT, stream‑level flow control, and real‑world adoption strategies.
0-RTTConnection IDGo
0 likes · 15 min read

The article traces the evolution of HTTP from the persistent‑connection design of HTTP/1.1 through the multiplexed, binary framing of HTTP/2 to the QUIC‑based HTTP/3, while also explaining status codes, cookies, caching directives, RESTful principles, WebSocket upgrades, and practical Python examples.
CachingHTTPHTTP/2
0 likes · 8 min read

This article traces the evolution from HTTP/1.1 to HTTP/3, explains how QUIC leverages UDP to achieve faster, secure connections, and details its handshake, connection migration, head‑of‑line blocking solutions, congestion and flow control mechanisms.
Flow ControlHTTPHTTP/3
0 likes · 14 min read

Version 6.1 of Swoole, built on Swoole v6.1.1 and PHP 8.4.14, introduces dynamic GCC support for Swoole‑CLI, a new random extension, libind2 and libpsl for Curl, upgrades PHP, numerous extensions, libraries, and switches HTTP/3 implementation, while fixing macOS build issues and deprecating ngtcp2.
HTTP/3Library UpdatesNetworking
0 likes · 3 min read

Despite widespread browser and CDN support for HTTP/3, most developers still struggle to deploy it end‑to‑end because of missing QUIC implementations in language runtimes, fragmented open‑source tooling, and compatibility issues with core libraries like OpenSSL.
HTTP/3OpenSSLQUIC
0 likes · 17 min read

The Go core team’s experimental HTTP/3 proposal, first introduced in 2024, has been postponed despite years of community demand, highlighting challenges in API design, backward compatibility, resource allocation, and the practical dominance of HTTP/2 over the newer protocol.
HTTP/3NetworkingQUIC
0 likes · 8 min read

This article explains how Java 24 and OpenJDK introduce HTTP/3 via JEP 517, describes the QUIC protocol that powers it, compares performance against HTTP/2, and provides Java benchmark code showing reduced latency and fewer TCP connections when using HTTP/3.
HTTP/3JavaQUIC
0 likes · 11 min read

This article explains how Java 24 and OpenJDK add HTTP/3 support, compares its speed to HTTP/2 using benchmark code, and shows why the QUIC‑based protocol delivers lower latency and fewer TCP connections for modern web applications.
HTTP/3JavaQUIC
0 likes · 13 min read

The Go core team proposes an experimental HTTP/3 implementation in the x/net/http3 package, outlining its background, development stages, sample code, and the potential benefits for compatibility, stability, and performance in backend networking.
GoHTTP/3Networking
0 likes · 7 min read

The article evaluates Reqable as a free, cross‑platform API testing tool, detailing its performance advantages over Postman, extensive feature set, data‑migration capabilities, HTTP/2‑3 support, active community contributions, and open‑source components, while providing concrete benchmark data and usage scenarios.
API testingHTTP/3Postman alternative
0 likes · 7 min read

This article demonstrates how to build high‑performance, low‑latency Go microservices by integrating gRPC with HTTP/3 over QUIC, covering server and client implementations, a sample Analyze service, step‑by‑step communication flow, and performance comparisons against traditional HTTP/2‑based gRPC.
GoHTTP/3QUIC
0 likes · 9 min read

ROFF is a Rust‑implemented, seven‑layer gateway that delivers high‑throughput load balancing with memory‑safe performance, TLS hardware offload, native QUIC/HTTP3 support, a hot‑reload/upgrade mechanism, and an extensible module system allowing over thirty built‑in filters and custom Rust macros.
GatewayHTTP/3Module System
0 likes · 28 min read

Niquests is a Python HTTP client that serves as a direct replacement for Requests, offering automatic support for HTTP/1.1, HTTP/2, and HTTP/3, along with advanced features such as DNS-over-HTTPS, async/await usage, and extensive security and performance enhancements.
HTTP ClientHTTP/3Niquests
0 likes · 6 min read

The article explains how Apache Dubbo's Triple X protocol now fully supports HTTP/3, detailing its design goals, performance advantages, configuration steps, code examples, and real‑world benchmarks that demonstrate significant latency reduction and reliability improvements in cloud‑native microservice environments.
DubboHTTP/3RPC
0 likes · 9 min read

Apache Dubbo’s new Triple X protocol now supports HTTP/3, enabling low‑latency, multiplexed, TLS‑1.3‑secured RPC calls that dramatically improve performance and reliability across cloud, cross‑region, and high‑loss networks, with detailed design goals, configuration steps, code examples, and benchmark results showing up to six‑fold gains.
HTTP/3Triple Xperformance
0 likes · 10 min read

This article explains WebTransport, an HTTP/3‑based API that offers multiplexing, flow control, and end‑to‑end encryption, compares it with WebSocket, and provides real‑world use cases such as cloud gaming and low‑latency live streaming with code examples.
HTTP/3QUICWebSocket
0 likes · 6 min read

This article traces the evolution of HTTP from its 1991 origins through HTTP/2 and HTTP/3, explains how QUIC leverages UDP to reduce latency, and details QUIC's connection establishment, migration, head‑of‑line blocking mitigation, congestion control, and flow‑control mechanisms.
BackendHTTPHTTP/3
0 likes · 13 min read

This article traces the evolution of HTTP from its 1991 inception through HTTP/1.1, HTTP/2, and HTTP/3, explains the QUIC protocol’s design and advantages, and details connection establishment, congestion control, flow control, and head‑of‑line blocking mitigation techniques used in modern web transport.
Flow ControlHTTPHTTP/3
0 likes · 15 min read

This article traces the evolution from HTTP/1.1 to HTTP/3, explains how QUIC built on UDP to reduce connection latency, avoid head‑of‑line blocking, support seamless connection migration, and introduce advanced congestion and flow‑control mechanisms that give HTTP/3 a performance edge over its predecessors.
Connection MigrationHTTPHTTP/3
0 likes · 14 min read

This article explains the evolution of HTTP from 1.1 to HTTP/3, introduces the QUIC protocol and its packet‑based design, and details how QUIC reduces RTT, solves head‑of‑line blocking, improves congestion and flow control, and supports connection migration.
HTTPHTTP/3QUIC
0 likes · 16 min read

The article thoroughly examines QUIC—the user‑space, UDP‑based transport underpinning HTTP/3—detailing its architecture, fast 0‑RTT handshakes, connection migration, stream‑level independence, congestion control, and flow‑control mechanisms, while also discussing implementation hurdles like 0‑RTT reliability, load‑balancer routing, UDP restrictions, CPU overhead, and real‑world performance gains reported by major Chinese tech firms.
0-RTT handshakeConnection MigrationHTTP/3
0 likes · 21 min read

This article explains how QUIC, a UDP‑based transport protocol developed by Google, overcomes TCP's limitations such as handshake latency and head‑of‑line blocking, offering lower latency, multiplexing, built‑in TLS 1.3 security, and why it powers the emerging HTTP/3 standard.
HTTP/3QUICTCP
0 likes · 12 min read

This article explains the evolution from HTTP/1.1 to HTTP/3, detailing QUIC's UDP‑based design, its impact on connection establishment, migration, head‑of‑line blocking, multiplexing, congestion control, forward error correction, and flow‑control mechanisms for modern web services.
BackendHTTPHTTP/3
0 likes · 15 min read

This article explains the evolution from HTTP/1.1 to HTTP/3, detailing QUIC’s UDP‑based design, its 1‑RTT handshake, connection migration, head‑of‑line blocking elimination, congestion‑control enhancements, forward error correction, and stream‑ and connection‑level flow control.
Flow ControlHTTP/3QUIC
0 likes · 16 min read


21CTOMay 31, 2024 · Backend Development
FrankenPHP, a Go‑based PHP application server built on Caddy, claims to double web request performance and halve developer/DevOps workload, offering container‑ready deployment, automatic HTTPS, native PHP extensions, in‑memory mode, structured logging, Prometheus metrics, and experimental HTTP/3 support.
CaddyContainerizationFrankenPHP
0 likes · 5 min read

This article surveys current front‑end innovations, covering Chrome extension development, using Husky for Git‑hook scripts, the clever architecture of Vite, new JavaScript operators (?., ??, ??=), the upcoming HTTP/3 protocol, 2024 front‑end technology trends, and an invitation to join a leading front‑end team.
2024 trendsChrome extensionsHTTP/3
0 likes · 4 min read


21CTOFeb 17, 2024 · Backend Development
Maxim Dounin launched the FreeNginx fork to free the popular Nginx web server from F5's corporate influence after disputes over an HTTP/3 vulnerability, highlighting broader geopolitical and open‑source governance challenges.
HTTP/3backend developmentfork
0 likes · 6 min read

The article explains how HTTP/3 abandons TCP in favor of the QUIC protocol built on UDP, detailing TCP's head‑of‑line blocking, handshake latency, middlebox rigidity, and how QUIC’s reliability, multiplexing, and fast handshakes address these issues while also noting deployment challenges.
HTTP/3NetworkingQUIC
0 likes · 7 min read

The curl 7.88.1 update addresses several critical bugs—including HTTP/2 multiplexed data corruption, inaccurate connection timeout handling, uninitialized port values in runtests, missing SRP support checks, HTTP3 fallback when HTTP2 is unavailable, and socketpair EWOULDBLOCK handling—enhancing reliability across platforms.
HTTP/2HTTP/3Networking
0 likes · 3 min read

An in‑depth look at HTTP’s origins, its client‑driven request‑response design, the evolution of headers, length‑ and delimiter‑based streams, and the successive enhancements from HTTP/0.9 through HTTP/1.1 to HTTP/2, SPDY, and HTTP/3, explaining the motivations behind each change.
HTTPHTTP/2HTTP/3
0 likes · 28 min read


21CTOJul 25, 2022 · Fundamentals
This article explains how HTTP/3, built on the QUIC transport, improves latency, reliability, and security compared to earlier HTTP versions, outlines its adoption across browsers and CDNs, and lists language libraries for developers to start implementing the new protocol.
HTTP/3QUICSecurity
0 likes · 7 min read

This article explains the evolution of HTTP from 1.1 to HTTP/3, how QUIC leverages UDP and TLS to achieve low‑latency 0‑RTT connections, solves head‑of‑line blocking, improves congestion and flow control, and why these advances matter for modern web applications.
HTTP/3QUICcongestion control
0 likes · 15 min read

This article explains the evolution from HTTP/1.1 to HTTP/3, highlights the limitations of HTTP/2 such as head‑of‑line blocking and TCP‑based latency, and shows how QUIC’s UDP‑based design, 0‑RTT handshakes, connection migration, and advanced congestion‑control mechanisms overcome those challenges to deliver faster, more reliable web traffic.
HTTP/3QUICTCP
0 likes · 14 min read

The article explains how TCP, the long‑standing transport for HTTP/1.x and HTTP/2, suffers from head‑of‑line blocking and handshake latency, why protocol ossification hinders upgrades, and how HTTP/3’s QUIC built on UDP overcomes these issues while introducing its own deployment challenges.
HTTP/3QUICTCP
0 likes · 7 min read

This article traces the development of the HTTP protocol from its earliest 0.9 version through 1.0, 1.1, 2.0, and the modern HTTP/3 over QUIC, detailing key features, header compression, multiplexing, caching mechanisms, server push, and the security and performance trade‑offs of each iteration.
CachingHTTPHTTP/2
0 likes · 20 min read

QUIC replaces TCP when long, lossy or wireless‑induced jitter dominates, offering multi‑stream, 0‑RTT, user‑space transport; Alibaba’s XQUIC library demonstrates 15‑20% latency cuts, 26% throughput gains via XDP‑based UDP bypass, and outlines a four‑stage adoption path from business value to open‑source leadership.
HTTP/3QUICUDP optimization
0 likes · 11 min read

This article explains the evolution of HTTP, the release of the HTTP/3 RFC, how QUIC leverages UDP to provide faster, secure connections with 0‑RTT handshakes, solves head‑of‑line blocking, improves congestion and flow control, and details its core mechanisms such as connection migration and ACK handling.
HTTP/3QUICTransport Protocol
0 likes · 14 min read

The article explains how HTTP/3, standardized as RFC 9114 after five years of work, replaces TCP with the UDP‑based QUIC protocol to overcome HTTP/1.1 and HTTP/2 limitations such as head‑of‑line blocking, improving multiplexing, congestion control, and security.
HTTP/3IETFNetworking
0 likes · 4 min read


ByteFEJun 10, 2022 · Industry Insights
This roundup covers the official release of HTTP/3 (RFC 9114), key findings from a 2022 frontend development survey highlighting TypeScript dominance, an in‑depth Web3.0 industry panorama, Douyin's Android power‑saving practices, bundler considerations, first‑party cookie guidance, content‑visibility performance analysis, and a detailed Three.js ice‑cream Earth tutorial.
Content-VisibilityFrontend DevelopmentHTTP/3
0 likes · 7 min read


21CTOJun 8, 2022 · Fundamentals
This article explains the significance of HTTP/3 for web performance, outlines its standardization history, compares it with HTTP/1.1 and HTTP/2, presents benchmark results, and discusses practical adoption considerations such as QUIC, 0‑RTT, and current implementation support.
HTTP/3NetworkingQUIC
0 likes · 9 min read


21CTODec 16, 2021 · Backend Development
This article explains the evolution of HTTP, compares HTTP/1.1, HTTP/2, and HTTP/3, and presents benchmark results from three global data centers showing how HTTP/3’s QUIC‑based multiplexing and 0‑RTT dramatically reduce page load latency.
HTTP/3QUICWeb Performance
0 likes · 13 min read

Since 2015, Ant Group’s Alipay client and gateway teams have been deploying QUIC, the next‑generation transport for HTTP/3, across mobile payment and overseas acceleration scenarios, detailing background, design choices, deployment frameworks, key technologies like connection migration, 0‑RTT, lossless upgrades, and related patents.
0-RTTConnection MigrationHTTP/3
0 likes · 20 min read

This article explains the historical development of the HTTP protocol—from the simple HTTP/0.9 version through HTTP/1.0, 1.1, the binary‑based HTTP/2, and the emerging HTTP/3—highlighting each version's features, limitations, and the motivations behind their upgrades.
HTTPHTTP/2HTTP/3
0 likes · 12 min read

QUIC, a UDP‑based transport protocol that merges TCP reliability, UDP speed, and TLS security, underpins HTTP/3 by eliminating TCP’s three‑way handshake and head‑of‑line blocking, offering connection migration, 0‑RTT latency, customizable congestion control, fully encrypted packets, and is already being deployed in services such as Tencent Cloud CDN.
Connection MigrationHTTP/3QUIC
0 likes · 17 min read

This article traces the evolution of the HTTP protocol from its early days through HTTP/1.0, 1.1, SPDY, HTTP/2, and finally to HTTP/3, explaining how QUIC over UDP addresses TCP's latency and security limitations while also highlighting remaining challenges.
HTTP/3QUICTCP
0 likes · 15 min read

This article reviews the development and core features of HTTP/2, explains why its TCP‑based design still suffers from head‑of‑line blocking and handshake latency, and argues that these inherent limitations make the transition to HTTP/3 over QUIC inevitable for modern web developers.
HTTPHTTP/2HTTP/3
0 likes · 12 min read

This article traces the evolution of HTTP from its 1991 origins through HTTP/1.0, 1.1, HTTP/2, and finally HTTP/3, explaining how QUIC over UDP addresses TCP’s latency and security limitations while also highlighting remaining challenges.
HTTP/3QUICTCP
0 likes · 12 min read

NetEase News adopted Google’s gQUIC via Chromium’s Cronet library together with Nginx + Caddy, making QUIC handle over 75% of traffic and cutting average response time by about 45%, halving error rates and reducing video stutter by more than 25% within three months.
AndroidCronetHTTP/3
0 likes · 13 min read

This article explains the evolution from HTTP/1.1 to HTTP/3, detailing QUIC's design, zero‑RTT connections, connection migration, head‑of‑line blocking elimination, multiplexing, congestion and flow control improvements, and why HTTP/3 is poised to become the next‑generation web protocol.
HTTP/3QUICnetwork protocols
0 likes · 18 min read

This weekly roundup shares practical front‑end knowledge, detailing step‑by‑step large file upload slicing with MD5 checks, strategies to replace bulky if‑else chains such as table‑driven maps and chain‑of‑responsibility, and concise overviews of HTTP/3’s QUIC origins and Deno 1.0’s Rust‑based runtime.
DenoFile UploadHTTP/3
0 likes · 5 min read

Microsoft announced on its official tech blog that it has open‑sourced MsQuic, its internal cross‑platform implementation of the experimental QUIC transport protocol, which underpins HTTP/3 and is already integrated into Windows, Microsoft 365, .NET Core, and SMB, offering performance and security improvements.
HTTP/3MicrosoftMsQuic
0 likes · 3 min read

This article explains what QUIC is, outlines HTTP/3’s advantages over HTTP/2, and provides step‑by‑step instructions with code samples for compiling Node.js’s QUIC implementation and running a simple QUIC server and client to observe protocol behavior.
HTTP/3Node.jsQUIC
0 likes · 8 min read


21CTONov 17, 2018 · Fundamentals
Upcoming IETF discussions aim to replace the long‑standing TCP‑based HTTP with a new UDP‑based protocol, QUIC, rebranded as HTTP/3, offering lower latency and improved security, while distinguishing Google’s gQUIC from the IETF’s iQUIC and gaining industry support.
HTTP/3IETFQUIC
0 likes · 4 min read

This article explains how the protocol formerly known as HTTP-over-QUIC was officially renamed to HTTP/3, outlines the role of the IETF QUIC working group, the distinction between iQUIC and gQUIC, and highlights key interoperability milestones and resources.
HTTP/3IETFNetworking
0 likes · 3 min read
