[tosti]

> using HTTP GET with a request body is a bad idea, as for example users behind a corporate firewall or a different browser may be unable to use your website.

So is using QUERY requests for quite some time from now.

[jy14898]

405 Method Not Allowed is trivial to fall back to POST. How do you know the GET request behaved incorrectly?

[tosti]

That's assuming the corporate proxy is well-behaved.

[jagged-chisel]

Then all bets are off, and I guess we just can’t HTTP ever again because a proxy can misbehave.

One should adhere to Best Practices since one cannot control every device between the app and the user. Best Practice says “GET has no body. QUERY can have a body. If QUERY fails (405), use POST with the body.” And eventually, enough proxies will behave well enough that at least the HTTP bit of the app has a chance of working.

[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".

[flanked-evergl]

The fact that some infrastructure is poorly maintained is not a reason against evolving protocols, it's a reason to maintain infrastructure better. It's really not that difficult to do.