From https://tools.ietf.org/html/rfc7231#section-4.3.1:
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.
(Some for HEAD/DELETE/CONNECT)
Perhaps we should relax this
I was originally thinking that this would be inconvenient for ES clients.
I could work around that. However for anyone attempting to build a
transparent proxy in front of ES (where they can't control client calls),
this would be an impossible to fix solution if a GET with body was
forbidden.
Hmm...
Spray currently allows this and products like ElasticSearch promote GET
bodies. This will be a breaking change for me as well once I migrate to
akka-http.
How opinionated are the developers here? Can this be more of a guideline
than a rule? :)
--
Read the docs:
Hi Kevin,
see
https://github.com/akka/akka/blob/release-2.3-dev/akka-http-core/src/main/scala/akka/http/model/HttpMessage.scala#L133
Cheers,
André
On Wednesday, April 15, 2015 at 4:51:33 AM UTC+2, Kevin Meredith wrote:
There's a Github issue, titled, 500 ISE for Client Side Error -
