<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flow Control on SoloSoft</title><link>https://www.solosoft.dev/tags/flow-control/</link><description>Recent content in Flow Control on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 19 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/flow-control/index.xml" rel="self" type="application/rss+xml"/><item><title>nginx 1.31.9 Measured: 28 Bytes to Mark a Busy Connection Reusable, and the 8,192-Byte Residue the Patch Left Behind</title><link>https://www.solosoft.dev/post/nginx-1319-http2-flow-control-measured/</link><pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/nginx-1319-http2-flow-control-measured/</guid><description>&lt;p&gt;On November 18, 2026, nginx shipped 1.31.9 (mainline) and 1.30.7 (stable) with ten CVEs fixed in one release. Four of them are rated &lt;code&gt;major&lt;/code&gt; on nginx.org, and the two HTTP/2 bugs in the middle of it — CVE-2026-123007 and CVE-2026-123633 — carry a CVSS 4.0 score of 9.2 in F5&amp;rsquo;s own CVE records. A Wiz blog post went up the same day; a Hacker News submission reached 1,103 points and 494 comments.&lt;/p&gt;
&lt;p&gt;The interesting part is not the severity. It is how small the fix is, and how much of the published narrative does not survive contact with the commit log.&lt;/p&gt;</description></item></channel></rss>