The new HTTP QUERY method explained

@Lensflare / @niggel bad decision. It actually makes me think about PROPFIND for WebDAV. I do not think it's worth a brand new method. And this is even worse:

Standard GET queries with data in the URL parameters are still perfectly fine. If there is no immediate need to change those to the QUERY method, leave them be.
If your users should be able to share or bookmark links of the filtered data, continue using GET requests. Sharing links as QUERY requests does not work.

It is perfectly fine. If it was that perfect (and it is) - why a freaking QUERY method? 😤

If you're building anything with real world latency constraints, the body parsing overhead on the server side will eat whatever minor benefit you think you're getting.

body parsing overhead is negligible compared to tcp connection setup