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

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

	▲	locknitpicker 12 minutes ago \| parent [-]
		> 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 2 hours ago | parent | prev | next [-]

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.

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

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

	▲	dotancohen 2 hours ago \| parent [-]
		Intermediate proxies, caches, CDNs, firewalls, and load balancers.