Feature: HTTP QUERY method (RFC 10008)

[EyJunge1]

Feature request

Support the HTTP `QUERY` method (RFC 10008 / OpenAPI 3.2 `query:`): safe, idempotent, request body allowed.

Problem

`QUERY` is currently treated as an unknown method (`HTTP_INVALID`) and the connection is aborted. There is no `HTTP_QUERY` bit, no `stringToMethod` / `methodToString` mapping, and `AsyncCallbackJsonWebHandler` cannot be bound to QUERY.

Solution

• Parse `QUERY` in the request line and expose `HTTP_QUERY`
• Keep body handling method-agnostic (already the case for `Content-Length` / chunked)
• Json handler: opt-in via `setMethod(HTTP_QUERY)` (do not add QUERY to the default GET/POST/PUT/PATCH mask)
• Map platform `http_method::HTTP_QUERY` only when `HTTP_PARSER_HAS_QUERY` is defined (the enumerator is not a `#define`)
• Optional: `Accept-Query` literal for RFC 10008 §3

Implementation

PR: #474

Related:

• ESP-IDF parser: feat(http_parser): add HTTP QUERY method (RFC 10008) (IDFGH-18266) espressif/esp-idf#19071
• Arduino-ESP32 WebServer body gate: WebServer: read request body for HTTP QUERY (RFC 10008) espressif/arduino-esp32#12895

[EyJunge1]

Implementation: #474

Related:

• ESP-IDF issue: http_parser: add HTTP QUERY method (RFC 10008) (IDFGH-18267) espressif/esp-idf#19072
• ESP-IDF PR: feat(http_parser): add HTTP QUERY method (RFC 10008) (IDFGH-18266) espressif/esp-idf#19071
• Arduino-ESP32 PR: WebServer: read request body for HTTP QUERY (RFC 10008) espressif/arduino-esp32#12895

[mathieucarbou]

@EyJunge1 : why closing ?

[EyJunge1]

@mathieucarbou I closed it because the issue template says issues are for bugs only. This one is a feature request (QUERY / RFC 10008), so I figured it did not belong here and the PR was enough.

Happy to reopen and leave it open until #474 is merged if you want feature work tracked as issues too.

[mathieucarbou]

@mathieucarbou I closed it because the issue template says issues are for bugs only. This one is a feature request (QUERY / RFC 10008), so I figured it did not belong here and the PR was enough.

Happy to reopen and leave it open until #474 is merged if you want feature work tracked as issues too.

Sorry - you are right!

The message needs to be updated done. We have so many people creating issues instead of discussions when they have support questions... Forgot about feature requests ;-)