[jbverschoor]

Yeah, query seems just GET with a body. No difference in protocol nor behavior

[gl-prod]

The difference is the method. Query you're saying I can use body. GET you should never use body.

[locknitpicker]

> The difference is the method. Query you're saying I can use body. GET you should never use body.

The biggest win is how intermediary boxes now have concrete guidance that a specific HTTP request is both safe, idempotent, and carries a request body. Up until now none of this existed, and at best developers could use unsafe methods to carry request bodies (see GraphQL and how it uses POST for queries)

[_flux]

There is the Accept-Query header https://www.rfc-editor.org/info/rfc10008/#appendix-A.3 that tells you can use QUERY. That's a bit different.

[ComodoHacker]

Except compatibility. If you're using classic GET and it's enough for you, you aren't affected.

[4gotunameagain]

What is compatible with a QUERY but not with a GET ?

[dotancohen]

Intermediate proxies, caches, CDNs, firewalls, and load balancers.

[4gotunameagain]

That is only in the case of GET with a body though.

[dotancohen]

Yes. That is the issue under discussion, e.g. not "classic GET".