<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Http on BitSpeed.org</title>
    <link>https://bitspeed.org/tags/http/</link>
    <description>Recent content in Http on BitSpeed.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bitspeed.org/tags/http/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP Transfer Timing Needs More Than a Stopwatch</title>
      <link>https://bitspeed.org/http-transfer-timing-needs-more-than-a-stopwatch/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bitspeed.org/http-transfer-timing-needs-more-than-a-stopwatch/</guid>
      <description>&lt;p&gt;Two HTTP requests can take the same total time for very different reasons. One may spend most of its observed interval establishing a connection. Another may receive its first response byte quickly and then spend longer reading the body. A stopwatch hides that distinction.&lt;/p&gt;&#xA;&lt;p&gt;Inspect records trace events and keeps the interval boundaries explicit. Some events can be missing or ambiguous. Concurrent connection attempts also make a neat additive waterfall less honest than it looks. The report leaves unavailable values unavailable instead of filling them with zeroes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
