RFC 10008: The new HTTP Query Method
Points and comments are a snapshot, not live.
RFC 10008 defines a new HTTP QUERY method for safe, idempotent queries with request bodies.
The RFC specifies the QUERY method as a safe, idempotent alternative to POST for queries that require a request body. Unlike POST, QUERY explicitly permits caching and automatic retries. Servers can optionally return a Location header to assign a URI to the query itself, or a Content-Location header to the result, enabling later GET requests. The method bridges the gap between GET (URI-limited) and POST (not inherently safe/idempotent), supporting use cases like complex GraphQL queries.
What commenters are saying
Commenters welcomed QUERY as a formal solution to the URL length limit for query parameters, noting it fits GraphQL queries well. Some questioned how idempotency is ensured without server state; others clarified that HTTP method semantics are conceptual, like GET, and app-level side effects (logging, quotas) are ignored. A minor debate arose over caching: critics argued that incorporating the request body into the cache key is impractical, while supporters emphasized that the method enables out-of-the-box infrastructure support for retries and caching.