<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rfc on CuraSec</title><link>https://curasec.metacog.co.kr/tags/rfc/</link><description>Recent content in Rfc on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 Sep 2026 14:58:07 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/rfc/index.xml" rel="self" type="application/rss+xml"/><item><title>IETF Publishes HTTP QUERY Method (RFC 10008): First New Verb Since PATCH</title><link>https://curasec.metacog.co.kr/insights/2026-09-18-http-query-method-the-grey-zone-between-get-and-post-fri-sep/</link><pubDate>Fri, 18 Sep 2026 14:58:07 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-18-http-query-method-the-grey-zone-between-get-and-post-fri-sep/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The new QUERY method sits between GET and POST semantics, meaning existing WAF rules, reverse proxies, and security controls may handle it inconsistently or not at all — worth understanding before adopting it in APIs or encountering it in the wild.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> A new HTTP verb with ambiguous semantics may appear in traffic without triggering existing method-based detection rules; no active exploitation context, but analysts should know to expect it in logs and WAF telemetry.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>