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
Elasticsearch does not handle some http methods properly #31017
Labels
Comments
Tim-Brooks
added
>bug
:Distributed/Network
Http and internode communication implementations
v7.0.0
labels
Jun 1, 2018
Pinging @elastic/es-core-infra |
That's not good! |
Also I think that we can and should backport any fix to 6.x, this is a bug indeed as you have already labeled. |
Tim-Brooks
added a commit
to Tim-Brooks/elasticsearch
that referenced
this issue
Jun 1, 2018
This is related to elastic#31017. That issue identified that these three http methods were treated like GET requests. This commit adds them to RestRequest. This means that these methods will be handled properly and generate 405s.
This has been merged into master. It still needs to be back ported to 6.x. |
Tim-Brooks
added a commit
that referenced
this issue
Jun 1, 2018
This is related to #31017. That issue identified that these three http methods were treated like GET requests. This commit adds them to RestRequest. This means that these methods will be handled properly and generate 405s.
Tim-Brooks
added a commit
to Tim-Brooks/elasticsearch
that referenced
this issue
Jun 4, 2018
This is related to elastic#31017. That issue identified that these three http methods were treated like GET requests. This commit adds them to RestRequest. This means that these methods will be handled properly and generate 405s.
Tim-Brooks
added a commit
that referenced
this issue
Jun 4, 2018
This is related to #31017. That issue identified that these three http methods were treated like GET requests. This commit adds them to RestRequest. This means that these methods will be handled properly and generate 405s.
The fix has been merged into master and 6.x. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently when we convert a low-level netty http method to an elasticsearch http method we consider an unknown request type to be a
GET
request.Currently that means that
PATCH
,TRACE
, andCONNECT
methods are treated asGET
methods by elasticsearch. If we do not plan on supporting these methods, we should just return a 405 instead of silently pretending that these areGET
requests.The text was updated successfully, but these errors were encountered: