HTTP QUERY Method: The Grey Zone Between GET And POST., (Fri, Sep 18th)
RFC 10008 standardizes the HTTP QUERY method, creating potential WAF inspection bypasses, cache poisoning, and CSRF gaps because most defenses don't recognize the new verb.
The IETF published RFC 10008 in June 2026 defining HTTP QUERY, the first new standard method since PATCH in 2010, behaving as a safe, idempotent, explicitly cacheable GET whose query lives in the request body. SANS handler Xavier Mertens warns that WAF rules, API-gateway allowlists, CSRF middleware, and caches built around the classic verb set may not inspect QUERY bodies, allowing SQL injection or XSS payloads to bypass inspection where POST would be blocked. Behavior in the wild is inconsistent: nginx's limit_except silently rejects QUERY and never caches it, while curl, Caddy, Traefik, FastAPI explicit routes, and .NET 10 pass or support it, and Cloudflare/Akamai co-authored the RFC. The author found no QUERY requests in his logs yet and recommends updating method-matching rules and allowlists to include QUERY.
- QUERY is a safe, idempotent, cacheable GET whose query lives in the request body (RFC 10008, June 2026).
- WAF signatures bound to POST bodies may miss SQLi/XSS payloads delivered via QUERY requests.
- Caches not keying on the full body risk poisoning; CSRF middleware may wave through state-changing QUERY endpoints.
- Server support is inconsistent: nginx limit_except rejects QUERY, while Caddy, Traefik, and .NET 10 handle it.
- Recommendation: update method allowlists, regexes, and WAF rules to explicitly include the QUERY verb.
- Vendors
- SANSnginxCloudflareAkamai
From the original article
3 min read at isc.sans.eduIn June 2026 the IETF published RFC 10008[1], defining a new HTTP method: "QUERY". The HTTP protocol faced already by changes (HTTP/2, HTTP/2) but it's the first new standard HTTP verb since "PATCH" in 2010!
isc.sans.edu
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.