HTTP QUERY Method: Web Standards Are Still Alive
The HTTP QUERY method is getting real attention, with commenters genuinely surprised that HTTP verbs are still evolving. The practical case is straightforward: right now, if you want to send a complex query with a request body, you're either abusing POST or cramming everything into GET query params. QUERY solves that cleanly by allowing a request body in a semantically read-only operation.
The thread is constructive and curious rather than combative, with people speculating about what request bodies will look like in practice. Most expect JSON, but someone floats the idea of putting computation directly in the body.
This is a small but real signal that the HTTP/REST layer is getting cleaned up. The existing methods have felt set in stone for developers who've been around for a while, and seeing a new one land is notable. Adoption timelines for new HTTP methods have historically been long, but the fact that there's active discussion and genuine use cases means it will eventually matter.
So what?
If you're designing APIs today, QUERY gives you a principled way to handle complex search and filter operations without the GET-with-body hack. It's worth watching the adoption curve on major frameworks and CDNs before committing to it in production, but starting to design with it in mind costs nothing.