<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Plan on BareProxy.com</title>
    <link>https://bareproxy.com/tags/plan/</link>
    <description>Recent content in Plan on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 30 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/plan/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How BareProxy Plan Shows What a Config Change Will Do Before It Goes Live</title>
      <link>https://bareproxy.com/how-bareproxy-plan-shows-what-a-config-change-will-do-before-it-goes-live/</link>
      <pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/how-bareproxy-plan-shows-what-a-config-change-will-do-before-it-goes-live/</guid>
      <description>&lt;p&gt;The riskiest moment in a proxy&amp;rsquo;s day is a config change. Cloudflare&amp;rsquo;s two outages at the end of 2025 both started with one that reached every server within seconds. BareProxy checks every config in full before it can go live, and &lt;code&gt;plan&lt;/code&gt; goes one step further: it says which requests will be handled differently.&lt;/p&gt;&#xA;&lt;p&gt;That works because BareProxy has no regular expressions and no scripting. Every matcher is an exact value, a prefix or a set, so the requests a site can receive fall into a finite number of classes, and every request in a class is handled the same way. &lt;code&gt;plan&lt;/code&gt; works out what happens to each class under the old config and the new one, and prints the classes that change.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
