GET vs POST for search

[abdollar]

I noticed the trace returns curl compatible output. As in:-

curl -X GET 'http://localhost:9200/blah/_search?pretty' -d ' ...

For curl, it looks like by default using the -d argument switches to a POST request by default -- the `-X GET' is necessary to keep it as a GET request, but the HTTP spec sorta implies that the body of a GET request is meaningless.

Here's a thread where someone else is wondering whether a GET having a body makes any sense - see http://stackoverflow.com/questions/978061/http-get-with-request-body

Is there a de-facto standard which treats parameters in the body as URL parameters except that they don't need to be fully url escaped?

elasticsearch supports a POST request - shouldn't that be the default or at least configurable since that conforms to standards.

[karmi]

Hi, so, I don't really wanna get into the "is GET with body RESTful or not" discussion :) I can see arguments on both sides of the debate. For what it's worth, Roy Fielding seems to be against he idea of body in a GET request.

On the Ruby side, yeah, totally agreed that it should be configurable. I would like to implement something like the Python client did in elastic/elasticsearch-py@cf03f98 soon.

[kcdragon]

Added PR #93 for this issue.

[asbjornu]

Related: elastic/elasticsearch#16024.