The Internet Engineering Task Force (IETF) has introduced a proposed new HTTP method called QUERY. This method is designed to support safe, idempotent requests with bodies, overcoming the limitations presented by existing methods such as GET and POST.
Traditionally, GET requests are constrained by URI length, limiting their ability to handle complex queries, while POST requests can manage more complex data in the body but are not inherently safe or idempotent—meaning they are not always suitable for repeated execution without unintended effects. QUERY offers a solution by allowing intricate queries to be encapsulated in the request body, while still supporting essential web operation features such as cacheability, automatic retries, and safe, predictable behavior on repeated requests.
The QUERY method extends HTTP’s powerful features by integrating the specification of URIs for query responses through the Content-Location and Location headers. This approach permits servers to provide universally identifiable URIs for query results, enhancing the web’s data accessibility.
Capability discovery is simplified via the Accept-Query header, allowing clients to understand the server’s support for the QUERY method. Additionally, the specification ensures effective caching strategies by ensuring that cache keys incorporate both the content and metadata of requests, promoting efficient data retrieval and management.
This advancement bridges the gap between the restrictive nature of GET and the flexibility but potential unpredictability of POST, paving the way for more expressive, reliable query operations in web communications.

Collections

The IETF has proposed a new HTTP QUERY method that enables safe, idempotent requests with request bodies. Unlike GET, which is limited by URI length, or POST, which isn't inherently safe or idempotent, QUERY allows complex queries in the request body while maintaining cacheability and predictable behavior. It supports capability discovery through the Accept-Query header and uses Content-Location and Location headers to provide URIs for query results, bridging the gap between GET's restrictions and POST's flexibility.

Introduction of the HTTP QUERY Method