discussion: very long secured api-keys cause problems while searching

We use very long secured API keys, which works fine with the 3.x version of the package but version 4.x breaks this, as the key seems to be appended to the URL regardless how long it is. It basically reintroduces this: #319. I think version 4 should also sent long api keys via the POST body.

Start by reproducing the long secured API-key search with the version 4.x client and compare its request behavior with 3.x. Review how the client builds requests for searches; the issue is done when long keys are sent in the POST body instead of being appended to the URL.

Written by the indexing model from the issue text.