[DavideCarvalho]

What

Adds first-class support for the QUERY HTTP method (RFC 10008), the safe, idempotent method that carries the query in the request body. It is meant for complex queries that don't fit in a URL.

• router.query(pattern, handler) shorthand, following the exact same pattern as router.get/post/put/patch/delete
• urlFor.query() on the URL builder (runtime + type definitions in client/types.ts)
• signedUrlFor.query() on the signed URL builder
• Content-Type enforcement: a matched QUERY route fails with E_INVALID_QUERY_CONTENT_TYPE (400) when the Content-Type header is missing or isn't a valid media type

router.any() was intentionally left unchanged to avoid altering the behavior of existing routes.

Why

Node.js parses the QUERY method out of the box on every version covered by this package's engines range (>=24.0.0; llhttp has shipped it since before v24.0.0, verified against deps/llhttp at the v24.0.0 tag), so routes defined with router.route(pattern, ['QUERY'], handler) already work today. This PR gives QUERY the same ergonomic, type-safe API as the other verbs.

RFC 10008 §2 says servers MUST fail the request if the Content-Type is missing or inconsistent with the content, and §2.1 recommends 400 for requests that lack media type information. The check runs in the route finder after a route matches and before the route middleware runs. So unknown routes still return 404, the bodyparser never reads the content of a rejected request, and the error goes through the app's error handler like E_ROUTE_NOT_FOUND.

The other §2.1 cases stay where the content is actually understood:

• unsupported media type (415): the bodyparser or the route decides
• content inconsistent with its type (400): already raised by the bodyparser's parse errors, e.g. invalid JSON

Body parsing is handled in adonisjs/bodyparser#86, and the docs in adonisjs/v7-docs#89.

Tests

• router.query() route definition with string controller and controller-tuple handlers
• urlFor.query() and signedUrlFor.query() coverage in the existing method-specific builder tests
• An end-to-end test that boots a real node:http server and dispatches a fetch(url, { method: 'QUERY', body: ... }) request through the router
• QUERY requests without a Content-Type, or with a malformed one ('', json, application/, ...), get a 400 and the handler is never called
• Valid media types (with parameters, unknown types like application/sql) are accepted
• The error reaches a custom error handler with code E_INVALID_QUERY_CONTENT_TYPE
• Other methods are not affected, and QUERY to an unknown route still returns 404

npm run quick:test (675 tests), npm run typecheck and the compile step (tsdown + tsc --emitDeclarationOnly) all pass. npm run lint passes on the changed files. A full eslint run currently reports 5 Prettier errors on lines this PR doesn't change. A clean 9.x checkout reports the same 5.

🤖 Generated with Claude Code

[thetutlage]

@DavideCarvalho Thanks for the PR. Can you please also send another PR for the docs covering this method. Since, QUERY is a new method, it will nice to share a tight summary of what this method is supposed to be used for and then maybe link to the spec or an article that covers it in a detail

[RomainLanz]

Hey @DavideCarvalho! 👋🏻

On top of what Aman said, we need to also update @adonisjs/bodyparser to populate the request.body() when the framework receive a QUERY request.

RFC 10008 also requires the server to reject QUERY requests with a missing or inconsistent Content-Type. Could you update your PR to enforce that?

[RomainLanz]

Any news @DavideCarvalho?

[DavideCarvalho]

Hey sorry, working on it today!

[DavideCarvalho]

Thanks for the patience! Updated:

• Content-Type enforcement (cfbb1cc): a matched QUERY route now fails with E_INVALID_QUERY_CONTENT_TYPE (400) when the Content-Type is missing or isn't a valid media type, per RFC 10008 §2/§2.1. It runs before the route middleware, so the body is never read. Unsupported types (415) and content that doesn't match its type (400) are still up to the bodyparser and the route. I also rebased on 9.x.
• Bodyparser: feat: parse the body of QUERY requests by default bodyparser#86 adds QUERY to the default allowedMethods
• Docs: docs(routing): document the QUERY HTTP method v7-docs#89