For over 15 years, backend developers, API designers, and frontend engineers have lived by a strict, self-imposed set of rules. If you want to create a resource, you use POST . If you want to replace it, PUT . If you want to fetch it, GET . But what happens when you need to fetch a resource using a massive, deeply nested JSON filter, a complex SQL string, or a large GraphQL block? Historically, we had to choose between breaking HTTP semantics or risking massive URL breakages. That era is officially over. In June 2026 , the IETF officially published RFC 10008 , standardizing a brand-new HTTP method: QUERY . This is the first major addition to the core HTTP verbs since PATCH was standardized back in 2010. Here is everything you need to know about why QUERY exists, how it works, and how it’s going to fix API design layout. The Broken Workarounds: GET vs. POST To understand why QUERY is such a big deal, we have to look at the architectural compromises developers have been force...
The story blog Internet is a big helper too.