[BUG] Unexpected behaviour if remote Opensearch response is not "common"

[zhavir]

Describe the bug
I'm trying to setup my pipeline with the Logstash and OpenSearch plugin. The connection seems working fine until the client tries to read the response received by the remote Opensearch instance.

To Reproduce
Difficult to reproduce because it is a self-hosted Opensearch instance with a proxy API on top

Expected behavior
no expectation raised

Plugins
Please list all plugins currently enabled.

Screenshots

Additional context
Add any other context about the problem here.

[dblock]

Looks like the plugin always expects JSON. That feels by design, doesn't it?

[zhavir]

there was a problem from my side, I was sure that I was trying to contact directly an OpenSearch instance. Instead, it was an Logstash. I've solved the issue by using the http plugin