Add support for the HTTP QUERY method (RFC 10008)#1319
Merged
Conversation
…uting, enable body parsing, and treat QUERY as unprotected in CSRF protection.
Member
|
💚 💙 💜 💛 ❤️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds first-class support for the new HTTP QUERY method, standardized in RFC 10008 (Proposed Standard, June 2026).
QUERY is safe and idempotent like
GET, but carries a request body likePOST— the request content (of any media type) defines the query. Because it is idempotent, a QUERY can be safely retried, unlikePOST.Changes
Plug.Router— add aquery/3convenience macro, mirroringget/3,post/3, etc. (Routing arbitrary verbs already worked viamatch/:via; this adds the ergonomic, discoverable verb macro.)Plug.Parsers— addQUERYto the methods whose body is parsed (previouslyPOST,PUT,PATCH,DELETE). This is the substantive change: a QUERY's body is its defining feature, so it now populatesconn.body_params/conn.paramsjust likePOST.Plug.CSRFProtection— treatQUERYas an unprotected method alongsideHEAD,GET,OPTIONS. QUERY is safe and cannot change state, so it does not require CSRF token verification; without this, QUERY routes behind a session/CSRF pipeline would be rejected.References