0 views collected around this technical thread.
cURL 8.1.2, the second patch of the 8.1.x series, introduces a range of bug fixes including corrected configure handling of $CC, improved nghttp2 linking without pkg-config, HTTP/2 and HTTP/3 EOF handling enhancements, libcurl.m4 cleanup, and libssh authentication fixes.
This guide explains how to use Python's httpx library and the curl command‑line tool to perform comprehensive HTTP/HTTPS testing—including basic requests, chunked transfers, HTTP/2, SSL/TLS configuration, and dynamic DNS resolution—complete with code examples and setup instructions.
This article details how an Android team unified multiple network libraries into OkHttp, integrated HttpDns to bypass carrier DNS hijacking, migrated to HTTPS and HTTP/2, and applied a series of performance and security optimizations that markedly improved request speed, reliability, and user experience across diverse mobile network conditions.
The article surveys the evolution of web communication from HTTP/1.x through HTTPS, HTTP/2, and HTTP/3, explaining request/response structure, methods, status codes, URIs, connection handling, cookies, caching, TLS encryption, and the performance‑boosting features of header compression, multiplexing, and QUIC‑based transport.
This article explains the fundamentals of the HTTP protocol, covering request preparation, message structure, methods, headers, caching, the request/response cycle, HTTP/2 enhancements, and the QUIC protocol's advanced features for faster, more reliable web communication.
This article outlines the background, guiding principles, measurement methods, and concrete optimization techniques—including protocol selection, data reduction, request aggregation, DNS and HTTP/2 improvements, priority handling, and backend tweaks—that together reduced SDK network latency by about 40% and accelerated asset delivery to over 90% within three seconds.
This article provides a comprehensive overview of the HTTP protocol, covering its fundamental concepts, request methods, status codes, common headers, caching mechanisms, security differences with HTTPS, and the evolution of the protocol through HTTP/1.1, HTTP/2, and HTTP/3.
The Poizon mobile app team reduced iOS and Android CDN request latency by up to 100 ms through adding regional edge nodes, upgrading to TLS 1.3, enabling OCSP stapling, and migrating traffic to HTTP/2, demonstrating that targeted CDN and protocol tweaks can deliver double‑digit performance gains with modest effort.
This article explains the fundamentals of HTTP, the differences between GET and POST, common status codes, HTTPS and TLS handshakes, the performance improvements of HTTP/2, binary framing, multiplexing, header compression, server push, QUIC, DNS resolution, and the complete browser loading process from URL to rendered page.
The article details Wukong’s systematic H5 performance overhaul—adding DNS‑prefetch, CDN and HTTP/2, compressing fonts and images, applying lazy‑load and WebP, minimizing reflows with Vue lifecycle hooks, using skeleton screens, and reporting metrics—resulting in load‑time cuts of up to 70 % and scores rising from the 40s‑60s to over 90.
The article explains how modern browsers manage TCP connections for HTTP requests, covering persistent connections, the limits on concurrent connections per host, the behavior of HTTP/1.1 pipelining, why SSL sessions may be reused, and how HTTP/2 multiplexing improves parallel request handling.
The article explains how modern browsers handle TCP connections and HTTP requests—including persistent connections, the limits on simultaneous connections per host, the (disabled) HTTP/1.1 pipelining, SSL reuse, and how HTTP/2 multiplexing improves image loading performance.
This article explains the browser rendering pipeline—from network communication and HTML/CSS parsing to DOM and render tree construction—highlighting common misconceptions, performance bottlenecks, and practical optimization strategies such as DNS reduction, TCP reuse, HTTP/2 features, efficient CSS selectors, and JavaScript loading techniques.
This article explains HTTP/2’s new features—HPACK header compression using static and dynamic tables with Huffman coding, and Server Push via PUSH_PROMISE frames—detailing how they reduce bandwidth, improve latency, and the underlying stream state machine, illustrated with code snippets and diagrams.
This article reviews the challenges of web performance, analyzes HTTP/1.1, HTTP/2, TLS, and QUIC protocols, discusses optimization techniques such as TCP fast open, TLS false start, server push, preconnect, and presents practical recommendations from the 2017 ArchSummit presentation.
Mobile pages load about 40% slower than PC pages, users abandon sites after three seconds, and this article offers practical frontend techniques—reducing HTTP requests, compressing assets, leveraging caching, and adopting HTTP/2—to dramatically improve mobile web performance.
This guide details a step‑by‑step process for dramatically improving a website’s load time—from analyzing page performance and optimizing images to using CDNs, merging and minifying assets with webpack, applying code‑level tweaks, and enabling HTTP/2 and gzip—resulting in a fourfold speed increase.