If you've built APIs for any length of time, you've almost certainly hit this wall: you need to fetch data based on a complicated set of filters, but GET can't carry a body, and cramming a nested filter object into a query string turns into an unreadable, size-limited mess. So you reach for POST instead — and now your "read" operation looks like a "write" to every cache, proxy, and retry mechanism between your client and your server.
That mismatch has existed since the early days of HTTP. As of June 2026, it doesn't have to anymore.
The IETF has published RFC 10008: The HTTP QUERY Method as a Proposed Standard — the first genuinely new, general-purpose HTTP method to reach standardization in years. It was authored by Julian Reschke, James M. Snell (Cloudflare), and Mike Bishop (Akamai), and it gives the web a method that behaves like GET in terms of safety and cacheability, while carrying a request body like POST.
The problem QUERY was built to solve
HTTP developers have historically had exactly two tools for "give me data based on these parameters," and neither one is quite right.
