Skip to content
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

Error 431 Request Header Fields Too Large with some API Keys #414

Open
jwells89 opened this issue Mar 16, 2024 · 0 comments
Open

Error 431 Request Header Fields Too Large with some API Keys #414

jwells89 opened this issue Mar 16, 2024 · 0 comments

Comments

@jwells89
Copy link

Describe the bug 🐛
For some users with a large number of permissions (increasing length of the API key), search fails with 431 Request Header Fields Too Large.

To Reproduce 🔍
Steps to reproduce the behavior:

  1. Set up a typical search client through instantsearch-android or other user of algoliasearch-client-kotlin
  2. Do a search with a long API key
  3. Observe described error

Expected behavior 💭
API key is sent in request body instead, producing no error and successfully searching.

Environment:

  • OS: Android 14
  • Version: instantsearch-android 3.3.0/algoliasearch-client-kotlin 2.1.9

Additional context
Some of our users have complicated, highly individual permissions which results in unavoidably long API keys. In the past, we encountered a similar issue in the iOS version of our app, which had the described fix applied and merged.

The now-archived algoliasearch-client-android which we had been using in our app previously behaved this way, but this was not carried over to algoliasearch-client-kotlin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant