June 17, 2026
QUERY? More like QTea
RFC 10008: The new HTTP Query Method
The web just got a new way to search, and the comments are already fighting about it
TLDR: A major web standards group approved a new request type called QUERY, meant to handle big search-style requests more cleanly than today’s clunky workarounds. Commenters were split between **finally, this fixes an old mess** and **do we really need another web method**, with one viral joke simply panicking that RFC numbers are already over 10,000.
The internet standards crowd has officially introduced a new web request called QUERY, and yes, the name is so blunt it almost feels like a joke. The big idea is simple: websites often cram searches and filters into a link, but those links can get too long, messy, and revealing. QUERY is meant to be the cleaner middle ground between the familiar "look something up" style and the more mysterious "send it as a form" workaround. In plain English: it gives websites a way to send bigger search requests without pretending they’re doing something more dramatic than a simple search.
But the real fireworks were in the community reactions. One camp was instantly thrilled, basically yelling, finally! User lanycrost cheered that query strings always had size limits and this could actually fix a long-standing annoyance. Toybeaver had the same energy, saying they were never a fan of awkward POST /search setups and were happy to see a cleaner option. Then came the skeptics. Brookst jumped in with the classic internet-developer mood: do we really need a whole new method for this? Their hot take was that adding tags to existing requests might already do the job, kicking off the usual standards debate of elegant fix or overengineered detour.
And of course, there was comedy. Pwdisswordfishq stared at the name "RFC 10008" and delivered the most relatable reaction in the thread: “Wait, it’s already past 10 thousand?” Meanwhile, one commenter immediately fast-forwarded to the chaos this could cause for browser bookmarks, because if QUERY really catches on, people will want their saved searches to come along for the ride. In other words, the spec may be official, but the comments section is where the real rollout drama has begun.
Key Points
- •RFC 10008 defines the HTTP QUERY method as a safe and idempotent way to send query instructions in the request body.
- •The RFC identifies practical drawbacks of using GET with query strings for large or complex inputs, including size limits, encoding overhead, and increased logging exposure.
- •The document notes that many systems use POST for queries today, but POST does not inherently indicate a safe, idempotent query operation.
- •QUERY is designed to combine body-based input handling with explicit safe and idempotent semantics, allowing features such as caching and automatic retries.
- •The specification also describes how servers may assign URIs to either the query itself or a specific query result for later retrieval via GET.