<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Caching on BareProxy.com</title>
    <link>https://bareproxy.com/tags/caching/</link>
    <description>Recent content in Caching on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/caching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Response Cache Plugin: Micro-Caching for Dynamic Sites</title>
      <link>https://bareproxy.com/bareproxy-response-cache-plugin-micro-caching-for-dynamic-sites/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-response-cache-plugin-micro-caching-for-dynamic-sites/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Status: planned, number 18 of 21 in BareProxy&amp;rsquo;s build order.&lt;/strong&gt; The plugins are built easiest first, and this one is about three or four days of coding: a cache has to be exactly right about what it may keep and share. It comes after the Auth gate plugin. This post describes what it will do, and it will be updated as it is built.&lt;/p&gt;&#xA;&lt;p&gt;A dynamic site often renders the same page for thousands of visitors in a row. A news front page, a product listing, an API endpoint that changes once a minute. Each request still goes to the app, and the app builds the same answer again. When a link gets shared widely, that is how a small server falls over.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
