Re:Microsoft REST API Guidelines
by paulddraper on Saturday November 23, 2019 @06:08PM
(#21617243)
A body is and has always been syntactically permitted on any HTTP request.
However, it is semantic nonsense to put it on a DELETE or GET.
DELETE is defined to remove the resource identified by the URL; GET is defined to fetch the resource identified by the URL. There no purpose for an entity.
Re:Microsoft REST API Guidelines
by littlestymaar on Sunday November 24, 2019 @07:45AM
(#21620075)
This is the point made in the SO answer I quoted, and this was the official position of the rfc2616[1], but as I said in my second edit, this rule was relaxed in the new version of the specification: rfc7231 published in 2014.
[1]: https://tools.ietf.org/html/rfc2616#section-9.3 [2]: https://tools.ietf.org/html/rfc7231#section-4.3.1
Re:Microsoft REST API Guidelines
by paulddraper on Sunday November 24, 2019 @08:56PM
(#21624871)
It looks more or less equivalent the situation previous.
> A payload within a GET request message has no defined semantics
Re:Microsoft REST API Guidelines
by littlestymaar on Sunday November 24, 2019 @09:15PM
(#21624932)
It went from
> The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI.
To :
> A payload within a GET request message has no defined semantics
Which, to me, sounds like: “it was forbidden to put info in the body, and now it's just not especially encouraged”. But maybe I'm over thinking the whole thing.
Edit: I was wrong. It's allowed to put a body in a GET request, but it isn't OK to use it according to the HTTP spec (which admittedly kind of weird). Source: https://stackoverflow.com/a/983458
Edit2: according to an edit int the SO response, it looks like I wasn't actually wrong: or at least not since 2014 when these RFCs[1][2] became the standard for HTTP.
[1]: https://tools.ietf.org/html/rfc7231#section-4.3.1 [2]: https://tools.ietf.org/html/rfc7230#section-3.3