@Mark Takata (Adobe) one of my coworkers ran into this issue again over the weekend and we were wondering if there are any updates on it? https://tracker.adobe.com/#/view/CF-4205407

Huh. Interesting. First time I'm seeing that. Let me wrap my brain around this, they are trying to use a BODY with a GET? I'm not going to share my opinion on that other than to say, I might have a chat with some folks. @Bagish Mishra can you flag this for discussion. My immediate gut reaction is to say "GET doesn't have BODY" but clearly ElasticSearch has made the opinionate decision to require it. I feel like there's other factors in play here also, if you can send a body in a get, I wonder if that opens attack vectors on an API that isn't expecting that parameter?

I've run into this with other APIs. The spec doesn't seem to specify either way. I initially thought it was weird to do that too, but it is what it is.

Yeah, the spec is unclear, which honestly is annoying. I think the issue here is whether this would break anything in GET for us. Or post a security issue, etc. Especially as it is "out of spec" as it were. But I'll chat with the team and, at minimum, get movement on the ticket one way or another.

It seems there are inconsistencies in other languages too on how this is handled. For me, since vendors are writing APIs that require this, then we need to support it.

ACK @Mark Takata (Adobe) @garciadev