Skip to content

Add QUERY method description to HTTP methods index #44568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gomestai wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Open

Add QUERY method description to HTTP methods index #44568

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions files/en-us/web/http/reference/methods/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,9 @@ Each request method has its own semantics, but some characteristics are shared a
- {{HTTPMethod("GET")}}
- : The `GET` method requests a representation of the specified resource.
Requests using `GET` should only retrieve data and should not contain a request {{Glossary("HTTP Content", "content")}}.
- {{HTTPMethod("QUERY")}}
- : The `QUERY` method requests that the target resource process the request {{Glossary("HTTP Content", "content")}} in a safe and idempotent manner and respond with the result.
It is similar to `GET`, but allows request content to be sent, for example when query parameters are too large or complex to fit comfortably in the URI.
Comment on lines +18 to +19

@hamishwillee hamishwillee Jun 30, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

  1. I think I'd put these (all) in alphabetic order, and same for the table below. My reason is that all HTTP methods are equal. It is better to therefore treat them as such.
  2. There is no need to link content again. First instance on page/list needed.
  3. I think the text here is pretty good, but perhaps at this level we should omit the for-example since none of the others have it. The alternative is to add an example to all the others.

So maybe reorder and do this?

Suggested change
- : The `QUERY` method requests that the target resource process the request {{Glossary("HTTP Content", "content")}} in a safe and idempotent manner and respond with the result.
It is similar to `GET`, but allows request content to be sent, for example when query parameters are too large or complex to fit comfortably in the URI.
- : The `QUERY` method requests that the target resource process the request content in a safe and idempotent manner, returning the result in the response.
It is similar to GET, but allows request body content with defined semantics.

- {{HTTPMethod("HEAD")}}
- : The `HEAD` method asks for a response identical to a `GET` request, but without a response body.
- {{HTTPMethod("POST")}}
Expand All @@ -38,6 +41,7 @@ The following table lists HTTP request methods and their categorization in terms
| Method | Safe | Idempotent | Cacheable |
| ------------------------- | ---- | ---------- | ------------- |
| {{HTTPMethod("GET")}} | Yes | Yes | Yes |
| {{HTTPMethod("QUERY")}} | Yes | Yes | Yes |
| {{HTTPMethod("HEAD")}} | Yes | Yes | Yes |
| {{HTTPMethod("OPTIONS")}} | Yes | Yes | No |
| {{HTTPMethod("TRACE")}} | Yes | Yes | No |
Expand Down