Kibana Devtools error "Does not support having a body"

We use ROR 1.35.0 ans ES 7.12.1,
when i use somme request GET or POST with Dev tools, for example :
GET /_index_template/
i have this error :
“error” : {
“root_cause” : [
“type” : “illegal_argument_exception”,
“reason” : “request [GET /_index_template/] does not support having a body”
“type” : “illegal_argument_exception”,
“reason” : “request [GET /_index_template/] does not support having a body”
“status” : 400

Can you Help us please,
Thank you

Hello @belotfi thanks for reporting this issue. We alreaady have a fix for this, and it will be present in the next release 1.36.0 which is due this weekend.

Hello Simon, Thank you, we wait the next release

Hi Simone,
it’s working now with ROR 1.36.0 for GET /_index_template/
but when i try to use this request with _bulk :

POST /xx-enrich-iis/_bulk
{ "index" : { } }
{ "nom": "ORCHESTxxx", "env_logique": ["Traitements xxxx","GSA xxx - xx - 01 : (xxxxI01)","Traitements de xxxx","Traitements xxx"], "niveau": "accepxxx" }
{ "index" : { } }
{ "nom": "ORCHESTRATEURFOR", "env_logique": ["Traitements xx","GSA xxx - EI - 01 : (xxxI01)","Traitements xxx","Traitements xxx"], "niveau": "formxxx" }
{ "index" : { } }

I got this :  
<!DOCTYPE html>
<html lang="en">
<meta charset="utf-8">
<pre>Bad Request</pre>

Thank you Simon for Help
1 Like

Thanks @belotfi. We’ll have a look!

Hello @belotfi. Thanks for your message. I can confirm that we found a bug related to POST _bulk on a plugin side, we are working on fixing it now

Is it possible to tell us when it will be available since we are strugling with ROR serveral months ago and each time there is a bug. I’m wondering if you perform tests with a good coverage before releasing a new versions !!! Now we have to meet a business deadlinne. we have missed several deliveries due to these problems and we are starting to doubt the reliability of the choice of ROR

1 Like

Hello @abdamou, thank you for feedback.

As a matter of fact, this morning @Dzuming took the time to add an extensive integration test suite dedicated to devtools alone. But yes, you are right we underestimated Devtools Kibana app and its apparent simplicity. It turned out having a few corner cases.

Root cause

  1. The initial bug: we always parse the body into JSON, which generated an empty object (even when dev tools request content-type wasn’t application/json). This caused does not support having a body error.

  2. POST _bulk kibana request body had content-type application/json but carried invalid JSON (non-standard double quotes, for some reason) so when we tried to parse it, it causes a 400 bad request error.


We won’t try to parse the body of ANY dev tools console request, as we really don’t make use of it in ROR logic after all.

Resolution Timeline

Maybe @Dzuming can confirm/correct me, but knowing his speed and typical work hours, I predict this fix will be delivered within the current day.

We will send you a pre-build ready to be installed.

By the way, please let us know if there are any other “hot spots” in Kibana functionality that are critical for your business case, and we should especially keep an eye on. We would be happy go beyond automated tests and go over those use cases manually.

Let me remark that as you are an enterprise customer, our support engineers, and myself are always at your disposal with top priority.