# The Query Method - A new HTTP verb > [!question] Lingering Questions > - How quickly do other frameworks (not just Laravel) and CDNs/proxies pick up QUERY support, and what breaks in the meantime for clients that send it to a server that doesn't recognize it? > - Does QUERY's "safe and idempotent, like GET, but with a body, like POST" property hold up cleanly for caching semantics, or does it need its own caching rules? > [!link] Cross Reference > - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — PII-in-access-logs is a hosting/security-stack concern this new verb directly addresses ## Metadata - Source: [[3. Resources/Literature Notes/The Query Method - A new HTTP verb]] - Author: Shawn Hooper - URL: https://shawnhooper.ca/2026/07/12/http-query-verb-rfc-10008/ ## Author's thesis The IETF published RFC 10008 in June 2026, defining QUERY — a new, standards-track HTTP method combining GET's safe/idempotent read semantics with POST's ability to carry a request body — letting sensitive data move out of the URL querystring (where it leaks into server access logs) and into the request body instead. Laravel 13.19 already ships support. ## Key arguments 1. **QUERY closes a real gap**: GET can't carry a body, so read requests needing structured input have long abused POST (breaking idempotency/safety semantics) or crammed everything into the querystring. 2. **The PII benefit is concrete and immediate**: moving sensitive query parameters into the body reduces how much of that data ends up logged in plaintext server access logs. 3. **This is already shippable, not speculative** — a standards-track RFC with a named framework (Laravel 13.19) already implementing it. ## Claim atoms This is a short news item without a full deep-read; no separate H3 claim-atom extraction beyond the thesis above. ## Permanent candidates - **The QUERY HTTP method moves PII out of access logs** — promoted below. ## Processing checklist - [x] Confirmed this is a thin source (news brief, no deep-read appendix) — created a lighter Literature Note per the thin-source path - [x] Promoted the one genuine claim - [ ] Watch for QUERY adoption beyond Laravel (other frameworks, CDN/proxy support) before treating it as broadly production-safe - [x] Connect into [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] ## Links - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — a new standards-track mechanism for reducing PII exposure in server logs