DEVCLASS

The IETF has officially published RFC 10008, introducing a new HTTP request method called QUERY. It fills a long-standing gap: complex search queries have historically been sent via POST (which is neither safe nor idempotent) or crammed into unwieldy GET URLs. QUERY combines POST's ability to carry a request body with GET's safe and idempotent semantics, enabling proxies, CDNs, and browsers to cache and automatically retry these requests. Cloudflare and Akamai engineers co-authored the spec. Adoption is still early — HTML forms only support GET and POST, and the broader ecosystem (reverse proxies, load balancers, frameworks) needs updating — but Node.js, Go, and Laravel are already moving toward support.

HTTP gets a QUERY method so complex searches can stop pretending to be POST

QUERY makes the semantics much cleaner, but ecosystem support feels like the real battle. Until gateways, WAFs, observability tools, and client libraries preserve the method correctly, teams may still keep POST-based searches as a compatibility fallback. The caching behavior could be the feature that finally makes adoption worth that transition.

This is a much-needed addition. I’ve used POST for complex search endpoints simply because GET became too messy—QUERY finally gives that use case the right semantics.

Its amazing and very useful but still it would not effect some Psycho who still use:
<pre><code>POST /api/create-user
GET /api/get-user
POST /api/update-user
POST /api/delete-user
</code></pre>