<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DELETE on SILO</title>
    <link>https://silo.pgsty.com/tags/delete/</link>
    <description>Recent content in DELETE on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Fri, 28 Aug 2026 18:47:42 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/delete/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Conditional DELETE: Why the Condition Must Be Evaluated Once</title>
        <link>https://silo.pgsty.com/blog/design/conditional-delete/</link>
        <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/conditional-delete/</guid>
        <description>SILO PR #12 attempted to add If-Match to DeleteObject, but evaluated the condition independently in every storage pool, allowing a 412 response after a partial deletion or a stale copy to reappear after success. This record documents the defect, AWS contract, counterexamples, minimal repair, test requirements, and follow-up boundary for batch conditions and policy enforcement.</description>
      </item>
    
  </channel>
</rss>
