LANGUAGES Signal 75
RFC 10008 Defines QUERY, Giving HTTP a Safe, Cacheable Read That Carries a Body
↗
RFC 10008, published in June 2026, standardizes the QUERY method as a safe, idempotent and cacheable HTTP verb that may carry a request body.
For engineers building search or read APIs, QUERY offers a standards-based alternative to either cramming rich filters into URL query strings or sending them through POST and losing cache behaviour. The method is opt-in: servers advertise support via the new Accept-Query field, and caches key on request content, so existing GET and POST paths are unaffected. Adoption will be slow because clients, proxies and CDN caches all need to recognise the verb before QUERY is dependable in production.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
RFC 10008, published in June 2026, defines QUERY as a safe, idempotent and cacheable HTTP method that may carry a request body, making it the first new standard HTTP verb since PATCH in 2010.
The method was authored by Julian Reschke, James Snell and Mike Bishop and is positioned by the IETF as an additive option alongside GET and POST rather than a replacement for either.
Support has merged into the Rust http crate and is tracked across .NET, Axum, Quarkus and Bruno, while servers signal QUERY support to clients through the new Accept-Query field.
THE CLUSTER