Allow for future use of HTTP QUERY method

[mwullink]

we may want to include support for the future QUERY METHOD

ref: https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/

[pawel-kow]

Do you see any use of it so far?
I haven't faced any GET use-case, which would require large payload that won't fit into query parameters.
QUERY may come into play if we start with bulk read use-cases. Like bulk CHECK. The list of domains may be long in theory, but would it in practice exceed the capacity of query string?

[mwullink]

now sure where to use it, i just want to make sure we can if we want to.

[KangoV]

I believe when using GET, there should be no body as RFC-7231 fails to define what should be done. Consequently, some HTTP servers allowed it. Others, like browsers, load balancers, and caching proxies, didn’t.

I think support for QUERY would be a good idea as the content body has clearly defined semantics.