<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Proxy Security on Nalar</title>
    <link>https://nalar.dev/tags/proxy-security/</link>
    <description>Recent content in Proxy Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/proxy-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP Request Smuggling Exploits Parser Disagreement</title>
      <link>https://nalar.dev/http-request-smuggling-exploits-parser-disagreement/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/http-request-smuggling-exploits-parser-disagreement/</guid>
      <description>&lt;h1 id=&#34;http-request-smuggling-exploits-parser-disagreement&#34;&gt;HTTP Request Smuggling Exploits Parser Disagreement&lt;/h1&gt;&#xA;&lt;p&gt;A reverse proxy and an application server can each parse the same byte stream according to rules that appear reasonable in isolation. Trouble starts when they reach different answers about where one request ends. Bytes treated as the tail of a request by the front end can become the start of another request at the back end, shifting the interpretation of traffic that follows on a reused connection.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
