<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Injection on Napat&#39;s Inverse Blog</title>
    <link>/tags/injection/</link>
    <description>Recent content in Injection on Napat&#39;s Inverse Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 24 Jun 2026 10:00:00 +0700</lastBuildDate>
    <atom:link href="/tags/injection/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>QUERY Is the New GET, and That&#39;s a Problem</title>
      <link>/2026-06-24-query-is-the-new-get-and-thats-a-problem/</link>
      <pubDate>Wed, 24 Jun 2026 10:00:00 +0700</pubDate>
      <guid>/2026-06-24-query-is-the-new-get-and-thats-a-problem/</guid>
      <description>An application-security narrative review of RFC 10008 — the new HTTP QUERY method. Five paragraphs of Security Considerations for a method that normalizes SQL, JSONPath, and XSLT as request bodies. Here&amp;#39;s what the RFC got right, what it under-specified, and why your CDN, WAF, and DLP pipeline are not ready.</description>
    </item>
  </channel>
</rss>
