What is the difference between this and allowing HTTP GET with Body?
A payload within a GET request message has no defined semantics;
sending a payload body on a GET request might cause some existing
implementations to reject the request.But presumably no-one is brave/foolhardy enough actually to redefine GET as having a semantic body because a bazillion different implementations (clients, servers and middle boxes) probably become non-compliant.
So what actually?
apps that didnt use GET Body, will not care anyway
apps that will use HTTP GET Body will be checked anyway
So, unless somebody downgrades HTTP Server then what could be the problem?
Granted they need to get support for QUERY too but at least it is more explicit then.
An official readonly flag to POST would have been more backwards compatible...
What if we allowed HTTP GET Body?
What's the difference between PUT and allowing DELETE with a body?