<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Open Standards on Lucas Pardue - Bits &amp;&amp; Pieces</title>
    <link>https://lucaspardue.com/tags/open-standards/</link>
    <description>Recent content in Open Standards on Lucas Pardue - Bits &amp;&amp; Pieces</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 08 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lucaspardue.com/tags/open-standards/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP Integrity Digests: Past, Present, and Future</title>
      <link>https://lucaspardue.com/2026/08/08/http-integrity/</link>
      <pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://lucaspardue.com/2026/08/08/http-integrity/</guid>
      <description>&lt;p&gt;The core HTTP specifications don&amp;rsquo;t define their own means of providing&#xA;integrity. Although &amp;ldquo;hop-by-hop&amp;rdquo; protocols underneath HTTP, such as TLS or QUIC,&#xA;provide integrity for HTTP message transactions, it isn&amp;rsquo;t enough. HTTP powers&#xA;massively distributed systems where intermediaries (aka proxies) are first-class&#xA;citizens. Coupled with that are the powerful semantics of HTTP resources and&#xA;representations.&lt;/p&gt;&#xA;&lt;p&gt;This post explores the past, present, and future of HTTP extensions that allow&#xA;for HTTP Integrity. We&amp;rsquo;ll cover core concepts, fields such as &lt;code&gt;Content-MD5&lt;/code&gt;,&#xA;&lt;code&gt;Digest&lt;/code&gt;, &lt;code&gt;Content-Digest&lt;/code&gt;, &lt;code&gt;Repr-Digest&lt;/code&gt;, &lt;code&gt;Unencoded-Digest&lt;/code&gt;, and more.&#xA;However, some foundational HTTP understanding needs to be established before we&#xA;can start. If you just want to jump into an interactive demo playground see my&#xA;&lt;a href=&#34;https://lucaspardue.com/integrity-demos&#34;&gt;HTTP Integrity Demos page&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
