Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistency with case handling of HTTP verbs #133

Open
markharwood opened this issue Apr 19, 2016 · 2 comments
Open

Inconsistency with case handling of HTTP verbs #133

markharwood opened this issue Apr 19, 2016 · 2 comments
Labels

Comments

@markharwood
Copy link
Contributor

Training course attendee pointed out that lowercase "get" works as HTTP verb with returning a document by id but using the _mget form of URL with a body listing >1 ID requires an upper case "GET" verb. Took them a while to figure out the inconsistency.

@nplatis
Copy link

nplatis commented Oct 9, 2016

I have another case where get does not work but GET works: in _search queries!
get seems to return all documents whereas GET works fine. The problem seems to be that, when using get the next lines are ignored: if I put the query body on the same line, it gets executed correctly

@vkroz
Copy link

vkroz commented Nov 22, 2016

Same problem exist in Sense bundled with Kibana 5.0.1 - lowercase 'get' doesn't work same way as uppercase 'GET' in search queries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants