For decades we've had exactly two bad options for "read something using a complex input": cram...
For decades we've had exactly two bad options for "read something using a complex input": cram everything into a GET URL, or lie and use POST. In June 2026, the IETF standardized a real fix:QUERY method (RFC 10008). Here's what it is, why it exists, and how to actually use it.
The problem: GET and POST both fall short
Say you have a search endpoint. The natural, RESTful choice is GET:
GET /contacts?select=surname,email&match=email=*@example.*&limit=10 HTTP/1.1
Host: example.org
RFC 10008 standardizes the HTTP QUERY method, finally closing the long-standing gap between GET and POST. Here's what it is, why…
For years, developers have faced the same dilemma when implementing complex search APIs: GET is...
RFC 10008 standardized the HTTP QUERY method in June 2026: safe and idempotent like GET, but able to carry a request body like…
For years, developers have faced a common dilemma when building REST APIs: How do you send a...
The HTTP protocol has remained surprisingly stable for years. But now, there's a new method that...
HTTP has a new request method: QUERY. For years, developers have mainly used GET to fetch...
