<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HTTP/3 on Volodymyr's Blog</title><link>https://vzav.eu/tags/http/3/</link><description>Recent content in HTTP/3 on Volodymyr's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vzav.eu/tags/http/3/index.xml" rel="self" type="application/rss+xml"/><item><title>HTTP/3 in Practice: From SPDY to QUIC on My Home Router</title><link>https://vzav.eu/posts/networking/http3/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://vzav.eu/posts/networking/http3/</guid><description>&lt;p&gt;I turned on HTTP/3 for a CloudFront distribution, saw the load times improve, and then did what I usually do when something works without me understanding why: I went looking for the packets.&lt;/p&gt;
&lt;p&gt;This post has three parts. First, how HTTP got here — because HTTP/3 makes very little sense without the twenty years of workarounds that preceded it. Second, the theory, kept short. Third, the practical part: enabling it on a CDN, then capturing real QUIC traffic on my OpenWrt router with &lt;code&gt;tcpdump&lt;/code&gt; and reading what comes back.&lt;/p&gt;</description></item></channel></rss>