4 ms·
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 i
by littlestymaar 7y ago
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 https://tools.ietf.org/html/rfc2616#section-9.3
[2]: https://tools.ietf.org/html/rfc7231#section-4.3.1 https://tools.ietf.org/html/rfc7231#section-4.3.1
- paulddraper 7y agoIt looks more or less equivalent the situation previous. > A payload within a GET request message has no defined semantics
- littlestymaar 7y agoIt 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.