Skip to content

feat(method): add QUERY method#798

Merged
seanmonstar merged 1 commit into
masterfrom
push-lxlvmqrmmnsp
Jun 16, 2026
Merged

feat(method): add QUERY method#798
seanmonstar merged 1 commit into
masterfrom
push-lxlvmqrmmnsp

Conversation

@seanmonstar

Copy link
Copy Markdown
Member

IESG has just confirmed promoting QUERY to Proposed Standard: https://lists.w3.org/Archives/Public/ietf-http-wg/2025OctDec/0208.html

@seanmonstar

Copy link
Copy Markdown
Member Author

Though, I wouldn't be opposed to waiting ever so slightly with merging this, to allow the IETF to finish, and include it in v1.5 instead of v1.4.

@seanmonstar

Copy link
Copy Markdown
Member Author

It has just been fully accepted today: https://www.rfc-editor.org/info/rfc10008/

So let's merge 😎

@seanmonstar seanmonstar merged commit bb8705b into master Jun 16, 2026
10 checks passed
@seanmonstar seanmonstar deleted the push-lxlvmqrmmnsp branch June 16, 2026 14:17
Comment thread src/request.rs
Comment on lines +411 to +413
// This is purposefully excluded because of potential conflict with the
// URI query.
// pub fn query() -> Builder

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bit late here, but could this be added as perhaps http_query if there is concern about a conflict?

For what it's worth, I don't find the conflict too worrisome: if there were a method to get the URI query, I'd expect that to be called uri_query, and this being a zero-param associated function (rather than a method to get the URI query, or a 1-param function to build a GET with one) is a pretty big clue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants