There may be use-cases (and the RFC allows ignoring the SHOULD clause with enough reasoning), but GET does not have a request body as per specification, and a LOT of things drop it because of that (most notably - nginx! Also applies to HAProxy and Apache HTTP server afaik, but also a bunch of load balancers)
There may be use-cases (and the RFC allows ignoring the SHOULD clause with enough reasoning), but GET does not have a request body as per specification, and a LOT of things drop it because of that (most notably - nginx! Also applies to HAProxy and Apache HTTP server afaik, but also a bunch of load balancers)
no.
Wrong.
Hint: Elasticsearch, GraphQL, Axios, etc..
GraphQL uses POST for queries.
Many GraphQL clients/libraries use GET with body to workaround hitting URL query limitations like length, etc.
Spec is not the same as compatibility.
How would you hit URL query limitations when putting your GraphQL query in the POST request's body?
[dead]