<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on BareProxy.com</title>
    <link>https://bareproxy.com/tags/security/</link>
    <description>Recent content in Security on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why BareProxy Routes on the Same Path It Forwards</title>
      <link>https://bareproxy.com/why-bareproxy-routes-on-the-same-path-it-forwards/</link>
      <pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/why-bareproxy-routes-on-the-same-path-it-forwards/</guid>
      <description>&lt;p&gt;Many proxy bypasses share one cause: the proxy reads a path one way and the application reads it another. A rule that blocks &lt;code&gt;/admin/&lt;/code&gt; does nothing if the request arrives as &lt;code&gt;/api/%2e%2e/admin&lt;/code&gt; and the application decodes it after the proxy has let it through.&lt;/p&gt;&#xA;&lt;p&gt;BareProxy normalizes every path once. It decodes escapes of plain characters, resolves &lt;code&gt;.&lt;/code&gt; and &lt;code&gt;..&lt;/code&gt; segments, and merges runs of slashes. Then it routes on that form and sends the backend exactly the same form. Encoded slashes and backslashes are refused unless a site opts in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
