<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Operations on RenderCache.com</title>
    <link>https://rendercache.com/tags/operations/</link>
    <description>Recent content in Operations on RenderCache.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 16 Oct 2026 18:00:00 +0300</lastBuildDate>
    <atom:link href="https://rendercache.com/tags/operations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Know which response left your server</title>
      <link>https://rendercache.com/response-receipts/</link>
      <pubDate>Fri, 16 Oct 2026 18:00:00 +0300</pubDate>
      <guid>https://rendercache.com/response-receipts/</guid>
      <description>&lt;p&gt;A cache hit does not necessarily mean a page body was delivered. A HEAD request can use a saved response and write zero HTML bytes. A conditional request can return 304. Redirects and removals preserve their own status, and a partial write can stop before the saved document is complete.&lt;/p&gt;&#xA;&lt;p&gt;RenderCache records response receipts after handling a recognized crawler claim. Cached response availability and full snapshot HTML are separate fields, alongside the method, actual status, cache outcome and body bytes accepted by the writer. Private and API bypasses are also visible when their traffic passes through the Go service. Selective edge routing can narrow that visibility, so the deployment topology matters.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
