Ever struggled to decide between GET and POST when building a search API? In June 2026, the first new HTTP method in 16 years, QUERY, was officially standardized as RFC 10008!
We break down this new method that gets the best of both worlds — a body like POST, but safe, idempotent, and cacheable like GET!
0:00 The GET-or-POST dilemma for search API methods
0:54 The limits of GET and the compromises of POST
2:15 The 4 gaps QUERY fills
3:06 Declaring support with the Accept-Query header
4:05 A world where the body is part of the cache key
5:02 GraphQL and the revival of CDN caching
5:53 Elasticsearch, BI dashboards, geo search — who benefits in practice
6:49 Node.js already works, Spring doesn't yet
7:45 One fetch call away, but watch out for CORS
8:31 How to start trying it today
9:27 If you're unsure, try it on a new search API first
▼Related Links
RFC 10008 (Official Spec)
https://www.rfc-editor.org/info/rfc10...
IETF Datatracker
https://datatracker.ietf.org/doc/rfc1...
Node.js Support Issue
https://github.com/nodejs/node/issues...
Spring Framework Support PR
https://github.com/spring-projects/sp...
MDN HTTP Methods (QUERY not yet included)
https://developer.mozilla.org/en-US/d...
Contact: [email protected]